[
http://jira.codehaus.org/browse/MASSEMBLY-501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Casey closed MASSEMBLY-501.
--------------------------------
Resolution: Fixed
use <useAllReactorProjects>true</useAllReactorProjects> inside a <moduleSet> to
enable access to all modules in the current reactor from binaries or sources.
> Define a method of using moduleSet/binaries from a child project to gain
> access to all modules in reactor
> ---------------------------------------------------------------------------------------------------------
>
> Key: MASSEMBLY-501
> URL: http://jira.codehaus.org/browse/MASSEMBLY-501
> Project: Maven 2.x Assembly Plugin
> Issue Type: New Feature
> Affects Versions: 2.2-beta-5
> Reporter: John Casey
> Assignee: John Casey
> Fix For: 2.2-beta-6
>
>
> Providing access to all modules in a reactor to a child project assembly will
> make moduleSet/binaries a viable option, since it allows the child project to
> run after all other projects. This will give it access to the binaries
> produced by sibling projects.
> Still need to work out whether there's a way to easily ensure it gets sorted
> down to the bottom...though I don't suppose that's necessarily required, as
> long as the modules it does depend on (through includes/excludes) are
> available by the time it builds. Project dependencies could always handle
> this, while the moduleSet usage would still open up avenues that
> dependencySets do not.
--
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
