Allow non-eager application of Gradle plugins #4162
Merged
Conversation
This file contains 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
shanman190
force-pushed
the
feature/gradle-apply-false
branch
from
662b5d3 to
8c1b0ce
Compare
shanman190
force-pushed
the
feature/gradle-apply-false
branch
from
8c1b0ce to
52f67e4
Compare
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.
What's changed?
Enable non-eager application of plugins.
What's your motivation?
As a Gradle user sometimes it is necessary to not eagerly apply a plugin, so that you can then later apply it in the project using alternative methods.
Anything in particular you'd like reviewers to focus on?
Nothing in particular.
Anyone you would like to review specifically?
Anybody.
Have you considered any alternatives or workarounds?
Have my own version of the recipe.
Any additional context
None.
Checklist