You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "John Casey (JIRA)" <ji...@codehaus.org> on 2007/07/14 00:30:13 UTC
[jira] Updated: (MASSEMBLY-220) unpacked assemblies render
different results when enumerating dependencies vs. using wildcards
[ http://jira.codehaus.org/browse/MASSEMBLY-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Casey updated MASSEMBLY-220:
---------------------------------
Fix Version/s: 2.2-beta-2
> unpacked assemblies render different results when enumerating dependencies vs. using wildcards
> ----------------------------------------------------------------------------------------------
>
> Key: MASSEMBLY-220
> URL: http://jira.codehaus.org/browse/MASSEMBLY-220
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-1
> Environment: mvn 2.0.6, jdk 1.4.2
> Reporter: Dirk Olmes
> Fix For: 2.2-beta-2
>
> Attachments: assembly-wildcard.xml, assembly.xml, pom.xml
>
>
> When using wildcards for assemblies which unpack jars, the contents of META-INF of the unpacked jars do not end up in the final JAR. This breaks systems which rely on the contents of the META-INF directory, e.g. Mule.
> I have attached a pom and two assemblies, one using wildcards and one enumerating all the dependencies. Run the assembly plugin on both descriptors and compare the resulting jars.
--
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