Add properties for Maven plugin versions #677
Merged
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
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.
jenkinsci/pomdefines properties for the versions of Maven plugins, which can be useful when testing a change to a Maven plugin in the contest of a Jenkins plugin build.jenkinsci/plugin-pomlacks this feature. This PR bringsjenkinsci/plugin-pomup to feature parity withjenkinsci/pomby defining properties for any Maven plugin versions used in this POM. If the same Maven plugin is used injenkinsci/pom, the same property name was used for consistency. No version numbers were changed. The integration tests should be sufficient to validate this change.