Use Gradle task avoidance #18
Open
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
|
Forgot to add the screenshots Before: After: |
This was referenced Aug 13, 2022
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.
This PR implements task avoidance inside the plugin, because it always configures JaCoCo (and in consequence the
testtask), even if it is not used in the build. To reproduce, create a build scan with./gradlew --scan helpand check the output as described in the "Troubleshooting" section in the manual. The current release shows 3 created tasks, the version with this PR applied shows 0.I also took the liberty too add the most recent major versions to the tests and make minor modifications so that the plugin can be used in a composite build with recent Gradle releases. (I needed that for manual testing and creating the build scans.)
Thanks for this great plugin!