Don't force the latest Maven 3.x patch release on the build #1172
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.
Yes, there might be systems which lag one or two minors behind.
Additionally, it's apparently in the talks for a while to deprecate
the
prerequisites
section. Adding to that, the description of themaven
-element is somewhat misleading as it says something aboutthe Maven version the plugin is to be used with but actually a check
for the buid Maven version is performed.
I opted to
3.0
, but I guess dropping it entirely would also work.