[
https://issues.apache.org/jira/browse/MNG-7804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17729985#comment-17729985
]
ASF GitHub Bot commented on MNG-7804:
-------------------------------------
hboutemy commented on code in PR #1147:
URL: https://github.com/apache/maven/pull/1147#discussion_r1221042171
##########
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
> add flexible goal ordering in phase
> -----------------------------------
>
> Key: MNG-7804
> URL: https://issues.apache.org/jira/browse/MNG-7804
> Project: Maven
> Issue Type: New Feature
> Components: Plugins and Lifecycle
> Affects Versions: 3.0, 3.9.2, 4.0.0-alpha-5
> Reporter: Herve Boutemy
> Assignee: Guillaume Nodet
> Priority: Major
>
> as documented in MNG-5987 and described in MNG-5539 or MNG-6051, goals order
> in a phase can't be defined in a flexible way
> Adding a flexible mechanism would be useful
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
