[
https://issues.apache.org/jira/browse/MNG-7804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17729103#comment-17729103
]
Herve Boutemy commented on MNG-7804:
------------------------------------
one option is to make "priority" field introduced in MNG-4335 =
https://github.com/apache/maven/commit/c249a984084b4143ecfa64dfd26fecfbb199057c
= transient priority field on plugin execution
https://maven.apache.org/ref/3.9.2/maven-model/maven.html#class_execution
dropping its transient config and putting it as XML attribute should be easy
and permit customization without adding much complexity in existing code: it's
already used for lifecycle plugins
IIUC, by default, priority is 0, default lifecycle plugin bindings are put -1
to ensure they are executed first: using any other value should influence order
> 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
> 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)
