[MNG-7804] Add flexible goal ordering in phase

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0, 3.9.2, 4.0.0-alpha-5
• Fix Version/s: 4.0.0-alpha-8, 4.0.0
• Component/s: Plugins and Lifecycle
• Assignee: Guillaume Nodet
• Reporter: Herve Boutemy
• Created: 04/Jun/23 16:28
• Updated: 14/Dec/23 14:41
• Resolved: 16/Oct/23 11:29

Description

The 4.0.0 model contains a priority field which is flagged as xml transient.
The 4.1.0 model which is introduced in alpha-8 changes the flag so that it is now part of the xml model.

The priority field must be an integer. The priority of a given execution is 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.

           <execution>
            <id>400. This should be fourth</id>
            <goals>
              <goal>run</goal>
            </goals>
            <phase>clean</phase>
            <priority>400</priority>
          </execution>

Issue Links

• fixes: MNG-6051 Different plugins' executions aren't sorted between them
• fixes: MNG-5539 Profile plugin execution order is not preserved when merging into default PluginContainer
• relates to: MNG-5987 Document the algorithm calculating the order of plugin executions inside a phase.
• supercedes: MNG-5994 add explicit ordering support for plugins
• links to: GitHub Pull Request #268
• links to: GitHub Pull Request #1147
• links to: GitHub Pull Request #1173
• links to: GitHub Pull Request #1284