Code Monkey home page Code Monkey logo

Comments (7)

tasomaniac avatar tasomaniac commented on June 1, 2024 1

I found a local solution like below to this situation:
https://github.com/tasomaniac/OpenLinkWith/blob/master/app/build.gradle#L9

I basically check if the file exists. If not I am putting a different debug signing properties.

from gradle-build-properties-plugin.

tasomaniac avatar tasomaniac commented on June 1, 2024 1

Here is how I did on my personal project:

def signingFile = file('props/release.signing')
buildProperties {
    signing.file signingFile.exists() ? signingFile : file('props/debug.signing')
}

from gradle-build-properties-plugin.

frapontillo avatar frapontillo commented on June 1, 2024

What if you override the default method with void file(File[] files, String errorMessage = null) so the fallback is transparent to the main use case?

from gradle-build-properties-plugin.

tasomaniac avatar tasomaniac commented on June 1, 2024

File level there are multiple ways of doing it and that would mostly be easy. It could also be vararg of File s.

I actually tried doing it. But I realized that it may not be parallel with the plugins intention. I think it make sense to assign 1 file to 1 object.

With or on the entity you can get the value from different objects anyways.

What do you think @mr-archano

from gradle-build-properties-plugin.

mr-archano avatar mr-archano commented on June 1, 2024

To be honest I'm not sure about the whole support of signing config: it's a little bit flawed in the way files are resolved as relative paths to the properties file and (most annoying to me) it will work only iff the file will comply to the given structure, that makes things a little bit fragile.

That said I'll think about it and let you know soon(ish). We can catch up about this IRL if you prefer.

Thanks for the interest tho! 👍

from gradle-build-properties-plugin.

tasomaniac avatar tasomaniac commented on June 1, 2024

I agree. Also we have getParentFile in Entries object. Entries doesn't really need to know about files. It is only used for signing configuration support to access to the path to resolve the keystore full file path.

from gradle-build-properties-plugin.

mr-archano avatar mr-archano commented on June 1, 2024

We haven't fully decided whether the signing config support will be removed. In the meantime I'm closing this issue because we agreed that or support for signing config is out of scope (but easily scriptable if needed).

from gradle-build-properties-plugin.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.