Resolved managed Maven plugin dependency versioning #417
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
oleg-nenashev
approved these changes
Nov 5, 2020
There was a problem hiding this comment.
I do not recall what exactly led to having these dependencies pinned explicitly. Likely it was a copy-paste at some point. Parent POM now includes recent versions for all Maven plugins it declares, so it should not be a problem to drop explicit version definitions
oleg-nenashev
changed the title
|
Thanks for the patch! |
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.
Removed explicit versioning to help eliminate conflicts for three parent managed dependencies
org.apache.maven.plugins.maven-assembly-plugin
org.apache.maven.plugins.maven-resources-plugin
org.jvnet.maven-antrun-extended-plugin.maven-antrun-extended-plugin