[
http://jira.codehaus.org/browse/MASSEMBLY-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaan Vajakas updated MASSEMBLY-395:
-----------------------------------
Attachment: my-app.assembly-plugin-2.2.zip
The problem is still present in assembly plugin 2.2 with Maven version 3.0.1.
Added new test project for assembly plugin 2.2: my-app.assembly-plugin-2.2.zip
(the old one gave an error with version 2.2 because the
binaries/useStrictFiltering element is not supported any more).
> Module dependencies not included
> ---------------------------------
>
> Key: MASSEMBLY-395
> URL: http://jira.codehaus.org/browse/MASSEMBLY-395
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-3
> Environment: Maven version: 2.0.9
> Java version: 1.5.0_09
> OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
> Reporter: Jaan Vajakas
> Attachments: my-app.assembly-plugin-2.2.zip, my-app.zip
>
>
> Maven assebly plugin 2.2-beta-3 does not include module dependencies, even
> when the explicit <includeDependencies>true</includeDependencies> is used in
> assembly descriptor. Maven assebly plugin 2.2-beta-2 did not have this issue.
> See the attached project: running mvn package for the parent project my-app
> creates a ZIP that contains only my-app-module1-1.0-SNAPSHOT.jar. If assembly
> plugin 2.2-beta-2 is used (i.e. if one replaces 2.2-beta-3 with 2.2-beta-2 in
> pom.xml of my-app) then the ZIP also contains my-app-module2-1.0-SNAPSHOT.jar
> and junit-3.8.1.jar.
--
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
