You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Thomas Swindells (JIRA)" <ji...@codehaus.org> on 2008/04/29 10:16:48 UTC
[jira] Commented: (MASSEMBLY-301) assembly:attach wrongly
renames/overwrites assemblies to the primary artifact
[ http://jira.codehaus.org/browse/MASSEMBLY-301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=132945#action_132945 ]
Thomas Swindells commented on MASSEMBLY-301:
--------------------------------------------
A work around seems to be to set appendAssemblyId to true but to have have an empty assembly id. However this would appear fragile as someone may come along later and decide that the id of an assembly shouldn't be empty.
> assembly:attach wrongly renames/overwrites assemblies to the primary artifact
> -----------------------------------------------------------------------------
>
> Key: MASSEMBLY-301
> URL: http://jira.codehaus.org/browse/MASSEMBLY-301
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-2
> Reporter: Dan Diephouse
>
> I've configure the assembly plugin in my project like so:
> <plugin>
> <artifactId>maven-assembly-plugin</artifactId>
> <configuration>
> <finalName>${artifactId}-${version}</finalName>
> <descriptors>
> <descriptor>assembly.xml</descriptor>
> </descriptors>
> <appendAssemblyId>false</appendAssemblyId>
> </configuration>
> <executions>
> <execution>
> <id>make-assembly</id><!-- this is used for inheritance merges -->
> <phase>package</phase><!-- append to the packaging phase. -->
> <goals>
> <goal>attached</goal><!-- goals == mojos -->
> </goals>
> </execution>
> </executions>
> </plugin>
> Note, that my project is producing a JAR artifact in addition to the zip/tar.gz artifacts produced by the assembly plugin. However, the assembly plugin in beta-2 feels the need to make the zip assembly the primary assembly and make it a jar!
> [INFO] [install:install]
> [INFO] Installing c:\workspaces\cxf\workspace\mule-transport-restlet\target\mule-transport-restlet-1.0-SNAPSHOT.zip to c:\repo\org\mule\transports\mule-transport-restlet\1.0-SNAPSHOT\mule-transport-restlet-1.0-SNAPSHOT.jar
> [INFO] [deploy:deploy]
> altDeploymentRepository = null
> [INFO] Retrieving previous build number from muleforge.webdav.snapshots
> Uploading: https://dav.muleforge.org/snapshots.repository/restlet//org/mule/transports/mule-transport-restlet/1.0-SNAPSHOT/mule-transport-restlet-1.0-20080321.175727-2.jar
> During that last line Maven is uploading the zip as the jar!
> Reverting back to 2.2-beta-1 fixies this.
--
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