Inconsistent documentation of minimum required Maven version #457
Labels
bug
Something isn't working
Milestone
Comments
|
Looking at this issue |
JOpsDev
added a commit
to JOpsDev/maven-it-extension
that referenced
this issue
Mar 20, 2024
… Maven version - 3.8.1 as been agreed upon to be the minimum for now - gh-pages need to refreshed from adoc - added link to contribution guide as well
JOpsDev
added a commit
to JOpsDev/maven-it-extension
that referenced
this issue
Mar 20, 2024
… Maven version - updated release notes
khmarbaise
pushed a commit
that referenced
this issue
Apr 13, 2024
…sion - 3.8.1 as been agreed upon to be the minimum for now - gh-pages need to refreshed from adoc - added link to contribution guide as well - updated release notes
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug:
In the README the min version is listed as
Apache Maven 3.8.4 or above.In the source code of the userguide docs it is listed as
Apache Maven 3.6.3 or above.And in the live gh-page which should be produced from that source code it is
Apache Maven 3.1.0 or above.Kinda on topic but not relevant to the bug described:
If a minimum Maven version is so crucial for the library/plugins to work, should they maybe enforce it via the requireMavenVersion enforcer rule?
The text was updated successfully, but these errors were encountered: