[MNG-5987] Document the algorithm calculating the order of plugin executions.

• Type: Improvement
• Status: Open
• Priority: Critical
• Resolution: Unresolved
• Component/s: Documentation: General
• Assignee: Unassigned
• Reporter: Christian Schulte
• Created: 03/Mar/16 07:08
• Updated: 09/Nov/20 09:28

Description

Users continuously report issues regarding the order of plugin executions: repeating that this order is not expected to be guaranteed inside a phase is not convincing for them.

The algorithm used to calculate the order of executions performed by Maven needs to be documented:

• declaration order in the POM
• inheritance merging from parent POM,
• merging of profiles and other plugin containers,
• the order of executions of multiple executions in the same lifecycle phase,
  etc.

Issue Links

• is related to: MNG-6295 Inherited plugins are not properly ordered after merging with profile plugins in some special cases
• is related to: MNG-6051 Different plugins' executions aren't sorted between them
• is related to: MNG-5994 add explicit ordering support for plugins
• relates to: MNG-3719 [regression] plugin execution ordering no longer POM ordered in 2.0.9
• relates to: MNG-3925 [regression] Wrong order of plugin executions after merge with executions inherted from parent
• relates to: MNG-4975 [regression] plugin executions injected from profile run before instead of after existing executions in the POM
• relates to: MNG-3522 Cannot define Mojo execution order explicitly
• supercedes: MNG-5478 Order of plugin execution does not match order of definition in profile
• supercedes: MNG-5799 Incorrect execution order of plugins in the same phase
• supercedes: MNG-5539 Profile plugin execution order is not preserved when merging into default PluginContainer