maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brett Porter (JIRA)" <>
Subject [jira] Updated: (MNG-1994) Execution order of child plugins is arbitrary if inheritance is involved
Date Thu, 12 Jun 2008 22:51:20 GMT


Brett Porter updated MNG-1994:

    Fix Version/s:     (was: 2.1)

> Execution order of child plugins is arbitrary if inheritance is involved
> ------------------------------------------------------------------------
>                 Key: MNG-1994
>                 URL:
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Inheritance and Interpolation
>    Affects Versions: 2.0.1
>            Reporter: John Didion
>            Priority: Critical
>         Attachments: mergePluginLists.txt
> This is related to MNG-1499, but different, and, in my opinion, equally important. It
makes sense that the order of plugin execution should be the same as it appears in the POM.
For example, I have two plugins: one that generates a batch file and one that executes it.
These plugins must run in order or the build will fail. However, the current implementation
of ModelUtils.mergePluginLists does not respect the order of child plugins.
> There is also a seperate bug in that the assembledPlugins map is being checked for the
presence of child plugins before adding them to the mergedPlugins list, but nothing is ever
added to assembledPlugins. So if a plugin exists in a parent and a child, it will end up appearing
twice in the child's plugin list.
> I have re-written this method to fix both these problems. See attached.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message