gnodet commented on code in PR #1147:
URL: https://github.com/apache/maven/pull/1147#discussion_r1221223015
##########
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:
> Maven is not the only one using these pom.xml, but many tools in the wild:
that's why we always avoided adding XML elements, but only added XML attributes
when really necessary = the only accepted changes (in addition to the "import"
value for dependencyManagement scope see attributes in
https://maven.apache.org/ref/3.9.2/maven-model/maven.html
>
> on build vs consumer, we'll need to again define what is consumer, but to
me, this strict convention on available elements in published POMs will remain
forever
What tools to you have in mind ? If our own parser can be quite lenient, I
don't see why other tools would not be able to do the same. We can't just
decide to never update the model just because _other tools_ are using it.
--
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]
