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

Make the POM work with java 17.0.1+ #85

Closed
wants to merge 1 commit into from

Conversation

michalszynkiewicz
Copy link

Change the range for java-17 profile activation to [17,).
According to https://maven.apache.org/enforcer/enforcer-rules/versionRanges.html this is the way to do it and the current way [17,*) makes the builds fail

fixes #84

Motivation:

Explain here the context, and why you're making that change, what is the problem you're trying to solve.

Conformance:

Your commits should be signed and you should have signed the Eclipse Contributor Agreement as explained in https://github.com/eclipse/vert.x/blob/master/CONTRIBUTING.md
Please also make sure you adhere to the code style guidelines: https://github.com/vert-x3/wiki/wiki/Vert.x-code-style-guidelines

Change the range for java-17 profile activation to `[17,)`.
According to https://maven.apache.org/enforcer/enforcer-rules/versionRanges.html this is the way to do it and the current way `[17,*)` makes the builds fail

fixes vert-x3#84
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

vertx-consul-client POM not valid with java 17.0.1+
1 participant