Remove build warnings introduced by Gradle 7.2#211
Merged
Conversation
google-cla
Bot
added
the
cla: yes
Collaborator
|
Thanks for noticing the problem and for doing all that to fix it |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Now builds in
mainprint several warnings caused by the Gradle Modules plugin. It was introduced by Gradle v7.2 introduced by 6c3f286. So I've investigated and found a solution: java9-modularity/gradle-modules-plugin#201The updated version has been released yesterday, so I'm suggesting this PR that applies the released version to remove warnings. I've confirmed that this change has removed warnings during the build in this workflow run.