[
https://jira.codehaus.org/browse/MASSEMBLY-725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=355343#comment-355343
]
Osvaldo Doederlein commented on MASSEMBLY-725:
----------------------------------------------
I have a similar problem but with goal order, not phase order. I'm using both
the Assembly plugin and the AppAssembler plugin, both are bound to the package
phase, and ordered so the Assembly plugin runs last. Worked perfectly with
2.4.1 (and latest release versions of all other plugins and also Maven), now
with 2.5 the AppAssembler runs last so the output is incorrect. Attempt to put
AppAssembler in prepare-package failed because then it misses jars created by
the Jar plugin, which is also bound to package.
> Fix phase ordering
> ------------------
>
> Key: MASSEMBLY-725
> URL: https://jira.codehaus.org/browse/MASSEMBLY-725
> Project: Maven Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.5
> Reporter: Kristian Rosenvold
>
> The execution order of the phases is random based on maven version and
> possibly java version. Documentation on site seems to indicate there is a
> given precedence, which is wrong.
> Fix precedence of phases; this will only affect resolution of "duplicate"
> elements in the archive
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
