Keep the codestart Gradle wrapper in sync with version configured #48506
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.
This is a follow-up of #48395 and it should be more future-proof and also easier to backport.
@ia3andy I have a question for you: in
devtools/project-core-extension-codestarts
, we also include a Gradle wrapper in thegradle-wrapper/
directory of the jar. Do you know if this is actually used or if we should drop this? I see commits in there from time to time to fix things but I don't understand why we would have two copies of the wrapper. Or is it to support older projects?