[
https://issues.apache.org/jira/browse/MNG-7804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17729972#comment-17729972
]
ASF GitHub Bot commented on MNG-7804:
-------------------------------------
hboutemy commented on code in PR #1147:
URL: https://github.com/apache/maven/pull/1147#discussion_r1220964499
##########
api/maven-api-model/src/main/mdo/maven.mdo:
##########
@@ -2646,6 +2646,15 @@
]]>
</description>
</field>
+ <field>
+ <name>priority</name>
+ <version>4.2.0+</version>
+ <type>int</type>
+ <description>The priority of this execution compared to other
executions which are bound to the same phase.
+ Executions derived from the default lifecycle have a negative
priority by default so that they are executed
+ before any custom plugin executions.
Review Comment:
nice description
idea: IIRC, priority is set to -1 for lifecycle bindings, where default
priority is 0
while introducing this priority, using -1000 instead of -1 would permit
users to insert between lifecycle binding and default 0 (and would start to
clarify why priority vales is not ideal, but just an easy opportunistic feature
to use only when necessary)
note for self: I also need to check that when bindings have been defined
with default priority, we can in a child pom just override the priority by just
putting execution id
> 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)
