Use Maven enforcer for Java and Maven minimum versions #789
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
* Use Maven enforcer to clearly indicate the need for Java 17 during build, as the usage of Java 8 on the classpath may lead to confusion. * Also enforce the same minimum Maven version as used in the Maven wrapper to ensure both mvn and mvnw create similar output.
timtebeek
added
documentation
timtebeek
approved these changes
May 21, 2024
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.
What's changed?
What's your motivation?
If one tries to build on a JDK less than 17, the error messages are rather confusing (because the maven compiler plugin complains about some unknown symbols only). Make the error more obvious by using Maven enforcer instead.
Checklist