-
Type:
Improvement
-
Status: Open
-
Priority:
Critical
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: Documentation: General
-
Labels:None
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.
- is related to
-
MNG-6295 Inherited plugins are not properly ordered after merging with profile plugins in some special cases
-
- Open
-
-
MNG-6051 Different plugins' executions aren't sorted between them
-
- Closed
-
-
MNG-5994 add explicit ordering support for plugins
-
- Closed
-
- relates to
-
MNG-3719 [regression] plugin execution ordering no longer POM ordered in 2.0.9
-
- Closed
-
-
MNG-3925 [regression] Wrong order of plugin executions after merge with executions inherted from parent
-
- Closed
-
-
MNG-4975 [regression] plugin executions injected from profile run before instead of after existing executions in the POM
-
- Closed
-
-
MNG-3522 Cannot define Mojo execution order explicitly
-
- Closed
-
- supercedes
-
MNG-5478 Order of plugin execution does not match order of definition in profile
-
- Closed
-
-
MNG-5799 Incorrect execution order of plugins in the same phase
-
- Closed
-
-
MNG-5539 Profile plugin execution order is not preserved when merging into default PluginContainer
-
- Closed
-