Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't force the latest Maven 3.x patch release on the build #1172

Merged
merged 2 commits into from Feb 9, 2021

Conversation

mweirauch
Copy link
Member

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 the
maven-element is somewhat misleading as it says something about
the 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.

mweirauch and others added 2 commits February 9, 2021 22:23
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 the
`maven`-element is somewhat misleading as it says something about
the 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.
@uweschaefer uweschaefer merged commit 5f7d878 into master Feb 9, 2021
@uweschaefer uweschaefer deleted the dont-force-latest-maven-3-version branch February 9, 2021 21:35
@uweschaefer
Copy link
Member

fair enough

@uweschaefer uweschaefer added this to the 0.3.10 milestone Feb 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants