[
https://issues.apache.org/jira/browse/MPOM-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17506405#comment-17506405
]
Herve Boutemy commented on MPOM-303:
------------------------------------
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
> Rename property maven.plugin.tools.version to mavenPluginToolsVersion
> ---------------------------------------------------------------------
>
> Key: MPOM-303
> URL: https://issues.apache.org/jira/browse/MPOM-303
> Project: Maven POMs
> Issue Type: Task
> Components: asf
> Affects Versions: ASF-25
> Reporter: Slawomir Jaranowski
> Priority: Major
> Fix For: ASF-26
>
>
> {{maven.plugin.tools.version}} was introduced in ASF parent 25 on 2022-02-20
> (one week ago)
> https://github.com/apache/maven-apache-parent/commit/5a878dcdc00439cf03d383096c62e9003b503bfe
> having a property starting with {{maven.}} is not a good practice, because
> this prefix is used by Maven itself:
> https://maven.apache.org/ref/3.8.5/maven-model-builder/#model-interpolation
> and {{plugin.tools}} should be more {{plugin-tools}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
