[COMMONSSITE-87] Commons Parent needs to run assembly plugin later

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 40
• Assignee: Unassigned
• Reporter: Sebb
• Created: 17/Apr/16 00:54
• Updated: 17/Apr/16 13:09
• Resolved: 17/Apr/16 13:09

Description

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.