[
http://jira.codehaus.org/browse/MASSEMBLY-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=265508#action_265508
]
David Tombs commented on MASSEMBLY-94:
--------------------------------------
John, do you consider this truly fixed or are you still looking for a cleaner
solution? The assembly-only child module workaround is OK except that it
requires some hack dependency manipulation to make it the last to build. This
means that developers must remember to fix the assembly child module when they
add or remove other modules--and we all know how that goes.
> 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
>
>
> *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
