jira-importer commented on issue #495: URL: https://github.com/apache/maven-apache-parent/issues/495#issuecomment-2771739625
**[Herve Boutemy](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=hboutemy)** commented I know we have older mix, both at Apache level and at Maven level again, it's about avoiding changing too much at Apache level, given it's easier to change at Maven level and eventually not trying to have now a common convention for plugins, dependencies, and any other thing that is a version and if we have a unique convention, camel case is really harder to read than dotted going back to Apache-level, in version 24 (which was well used, not yet 25) https://github.com/apache/maven-apache-parent/blob/061e19af986a914df4d37b14e7e53a079d9033c5/pom.xml#L82 we have `surefire.version` (since release 18 in 2016), `minimalMavenBuildVersion` and `minimalJavaBuildVersion` since 24 then let's go to `minimal.maven.build.version`, `minimal.java.build.version` and `plugin-tools.version` = what costs less to Apache projects and we'll do the updates to Maven POM for consistency -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
