[
https://issues.apache.org/jira/browse/COMMONSSITE-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb resolved COMMONSSITE-87.
-----------------------------
Resolution: Fixed
Fix Version/s: 40
URL: http://svn.apache.org/viewvc?rev=1739560&view=rev
Log:
COMMONSSITE-87 - ensure assembly plugin runs after all package phase plugins
Modified:
commons/proper/commons-parent/trunk/pom.xml
> Commons Parent needs to run assembly plugin later
> -------------------------------------------------
>
> Key: COMMONSSITE-87
> URL: https://issues.apache.org/jira/browse/COMMONSSITE-87
> Project: Commons All
> Issue Type: Bug
> Reporter: Sebb
> Fix For: 40
>
>
> The parent pom runs the assembly plugin as part of the 'release' profile.
> The plugin is bound to the package phase.
> However it does not work reliably because the assembly plugin generally needs
> to use resources created in the package phase, so needs to run last.
> Although the assembly plugin is defined last in the release profile, if a
> component pom needs to add other plugins to the package phase, these will run
> later.
> The work-round in the past was to run the package phase twice, e.g.
> mvn package deploy
> [The second run of the assembly plugin will have access to the files created
> after its first run.]
> A possible solution is to bind the assembly plugin to the verify phase.
> This has been shown to work in the NET component pom.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
