-
Notifications
You must be signed in to change notification settings - Fork 100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The plugin is ignoring my custom file when specific the file with path. #39
Comments
Reading from another folder is not possible at the moment. If this is useful for others as well it can certainly be implemented. |
I see, thank you for letting me know |
It'd be nice to have this. I am trying to use this plugin in multiple modules with a single properties file. |
hi, instead of getting root project in SecretsPlugin.kt file:
you can change to:
this change load properties from current module: however you should be aware about how the plugin work, I mean if you don't declare a file path in the plugin extension config for properties, you should at least have local.properties file in any module you want to use plugin or maybe you can change this logic as well.
also I'd like to have a regex for properties files,
this force the properties files to start with in addition, if you like to have boolean and integer variable in you BuildConfig too you can change these line too:
|
As the document said we have to create a custom file at the root of the folder and it's working fine on my project,
Is it possible to move my custom file into another folder?
staging { secrets { propertiesFileName 'properties/staging.properties' } }
The plugin is ignoring my custom file with the path and then somehow read from my release.properties instead.
Does anyone know how to read the configuration file from another folder?
The text was updated successfully, but these errors were encountered: