[
http://jira.codehaus.org/browse/MASSEMBLY-201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Casey closed MASSEMBLY-201.
--------------------------------
Assignee: John Casey
Resolution: Cannot Reproduce
I'm guessing this was fixed in 2.2-beta-2, but the proof that this is fixed in
the 2.2-beta-3 code is in the following integration test:
http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-assembly-plugin/src/it/projects/dependency-sets/massembly-201
> classifier not included in name of dependency set
> -------------------------------------------------
>
> Key: MASSEMBLY-201
> URL: http://jira.codehaus.org/browse/MASSEMBLY-201
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-1
> Environment: 2.2-beta1 assembly plugin
> Reporter: Steve Berczuk
> Assignee: John Casey
> Fix For: 2.2-beta-3
>
>
> in my assembly descriptor I have
> <dependencySet>
> <outputDirectory>/dir</outputDirectory>
> <unpack>false</unpack>
>
> <includes>
> <include>com.berczuk:appdeps:zip:linux</include>
> <include>com.berczuk:appdeps:zip:win32</include>
> <include>com.berczuk:appdeps:zip:sunos</include>
> </includes>
> </dependencySet>
> with the 2.1 plugin my assembly package would create a zip file that
> contained the following files:
> dir/
> appdeps-1.1-linux.zip
> appdeps-1.1-win32.zip
> appdeps-1.1-sunos.zip
> now, there is only one zip file named appdeps-1.1.zip
> even if I change the outputFileNameMapping to include the classifier the
> classifier does not appear.
> This is a problem since it seemed to work so well before:)
--
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
