gnodet commented on code in PR #1147:
URL: https://github.com/apache/maven/pull/1147#discussion_r1222505682
##########
api/maven-api-model/src/main/mdo/maven.mdo:
##########
@@ -2646,6 +2646,15 @@
]]>
</description>
</field>
+ <field>
+ <name>priority</name>
+ <version>4.2.0+</version>
Review Comment:
> it is the convention that has been defined from the beginning for the
whole consumer ecosystem, and the reason build bom vs consumer pom has been
introduced
https://cwiki.apache.org/confluence/display/MAVEN/Build+vs+Consumer+POM
>
> we can test options and go back to the M dev ML to have feedback from
others: this change is not only about our internal code
I think the initial assumption and driver for the build/consumer feature,
i.e. that "changing the POM version and publishing artifacts on Maven Central
with this new model would break consumers using either older Maven versions or
other build tools" was done with a wrong assumption. I'll double check with
more tests, but afaik, consumers using old versions of maven won't be broken
when _using_ the artifacts as a dependency (they would be broken if using such
a project as a parent though). So yes, this definitely would mean that if you
use a 4.2.0 modelVersion (though you should not be forced to unless you
actually need something in it) imposes to use a recent maven when building a
project that inherit it.
I'm not sure about other tools.
Anyway, I'll send a mail to dev@ to discuss that.
--
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]
