You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Romain Manni-Bucau (JIRA)" <ji...@apache.org> on 2016/04/04 16:07:25 UTC
[jira] [Created] (MNG-5994) add explicit ordering support for
plugins
Romain Manni-Bucau created MNG-5994:
---------------------------------------
Summary: add explicit ordering support for plugins
Key: MNG-5994
URL: https://issues.apache.org/jira/browse/MNG-5994
Project: Maven
Issue Type: New Feature
Affects Versions: 3.3.9
Reporter: Romain Manni-Bucau
Hi
On one side maven doesn't really support plugin ordering in a deterministic manner (on some doc the merging mecanism states it follows the pom ordering but with some exceptions making a pom rarely deterministic and user friendly or at a very very high cost when pom hierarchy + profile are there).
On another side it is more and more common to need to add some custom processing (another plugin, a main through mvn-exec or a groovy script) between 2 plugins. Very common use cases are frontend optimizations, documentation generation etc...
That's why I'd like maven to support an explicit ordering. It can be as easy as adding to plugin a before/after tag(s) referring execution id of another plugin.
This would allow end users to explicitly control their whole build chain without having to hack maven with either meta-tasks, custom mojo or worse custom lifecycle. This would also finally allows users to remove workaround using wrong phases to ensure of the ordering for instance.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)