[
http://jira.codehaus.org/browse/MASSEMBLY-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Casey closed MASSEMBLY-94.
-------------------------------
Resolution: Fixed
Fix Version/s: (was: 2.3-beta-1)
2.2-beta-6
Assignee: John Casey
The solution to this design issue (from Maven itself) is to create a child
module solely to house the assembly. From this child, you can specify
dependencies such that the child is built last in the multimodule build process.
Then, you can use moduleSets along with the new
<useAllReactorProjects>true</useAllReactorProjects> flag inside the moduleSet
section to gain access to all projects currently in the reactor, and process
modules selected from that set.
> moduleSet/binaries doesn't work with assembly:single bound to the build
> lifecycle
> ---------------------------------------------------------------------------------
>
> Key: MASSEMBLY-94
> URL: http://jira.codehaus.org/browse/MASSEMBLY-94
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.1
> Reporter: Edwin Punzalan
> Assignee: John Casey
> Priority: Critical
> Fix For: 2.2-beta-6
>
>
> *Title was:* "reactorProjector projects have null Artifact files when using
> assembly:assembly"
> So the work-around is to use "mvn package assembly:assembly"... also,
> assembly:attached doesn't have this problem.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
