fix(doc): Fix incorrect defaults for nexus- and central-analyzer in gradle plugin documentation #5503
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
…radle plugin documentation Also extend the description to indicate cases that can benefit from enablement. Fixes documentation in relation to issue #5206
jeremylong
approved these changes
Feb 25, 2023
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.
Fixes Issue #5206
Description of Change
Fixes incorrect documentation of the analyzer enablement defaults of the Gradle plugin. Also adding some more detail regarding a logical reason to enable it (archives embedded in your project's dependencies that don't have maven meta-information available)
Have test cases been added to cover the new functionality?
no, documentation update only