apply user configuration before plugins' configuration to provide external properties #879
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
💔 |
|
💔 |
1 similar comment
|
💔 |
|
run ci |
|
💔 |
|
Jenkins CI fails because of the different directory structure defined by the changes to the project + Android Studio integration. Code and Scripts build successfully however. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Apply the user-defined configuration of
app.gradlebefore any other plugin-defined configs, during a Gradle build.Doing that will ensure that project-external properties defined as
project.extwill be available throughout the configuration step for plugin gradle scripts.Finally the user configuration will be reapplied, in order to apply settings the plugin scripts might have overridden.