[
https://jira.codehaus.org/browse/MASSEMBLY-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Rosenvold closed MASSEMBLY-395.
----------------------------------------
Resolution: Fixed
Fix Version/s: 2.5.1
Assignee: Kristian Rosenvold
Fixed in r1636510, thanks for the testcase! Please note that you *Must* specify
something like
<outputFileNameMapping>${artifact.artifactId}.${artifact.extension}</outputFileNameMapping>
for your testcase to work. This is a different issue, and I'm looking into that
> Module dependencies not included
> ---------------------------------
>
> Key: MASSEMBLY-395
> URL: https://jira.codehaus.org/browse/MASSEMBLY-395
> Project: Maven Assembly Plugin
> Issue Type: Bug
> Components: moduleSet
> 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
> Assignee: Kristian Rosenvold
> Fix For: 2.5.1
>
> 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 was sent by Atlassian JIRA
(v6.1.6#6162)
