[
http://jira.codehaus.org/browse/MASSEMBLY-443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg updated MASSEMBLY-443:
--------------------------------------
Fix Version/s: (was: 2.2)
> Module Sets don't support flat hierarchy of projects
> ----------------------------------------------------
>
> Key: MASSEMBLY-443
> URL: http://jira.codehaus.org/browse/MASSEMBLY-443
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-4
> Reporter: Marshall Schor
> Assignee: John Casey
> Priority: Minor
>
> If a multi-module project is using a flat hierarchy of projects, including
> the POMs, or a mixed hierarchy, and specifying modules like:
> <modules>
> <module>../../XXXproject</module>
> <module>../../YYYproject</module>
> </modules>
> the moduleSet mechanism doesn't find the modules, and nothing is included.
> If the layout is changed to the standard hierarchical one, then the very same
> assembly descriptor works.
> The assembly descriptor was pared down in my testing to just this:
> <assembly>
> <id>bin</id>
> <formats>
> <format>tar.gz</format>
> <format>zip</format>
> </formats>
> <includeBaseDirectory>false</includeBaseDirectory>
> <moduleSets>
> <moduleSet>
> <sources>
> <fileSets>
> <fileSet>
> <directory>src</directory>
> </fileSet>
> </fileSets>
> </sources>
> </moduleSet>
> </moduleSets>
> </assembly>
> Note that the non-hierarchical (flat) layout works for all of our other maven
> operations (except "release" - but I see that may have been also fixed in
> /MRELEASE-261 - haven't tried that...)
--
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
