[
http://jira.codehaus.org/browse/MASSEMBLY-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Casey closed MASSEMBLY-234.
--------------------------------
Assignee: John Casey
Resolution: Won't Fix
Fix Version/s: 2.2-beta-2
Use the assembly:attached or (better) the assembly:single goal if you want your
assembly archives to be attached to the outgoing project artifact. This is well
documented in http://maven.apache.org/plugins/maven-assembly-plugin
> Artifacts not deployed
> ----------------------
>
> Key: MASSEMBLY-234
> URL: http://jira.codehaus.org/browse/MASSEMBLY-234
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-1
> Environment: Windows XP, Maven 2.0.7, Java 1.5.0_09, latest version
> of all conspiring Maven plugins
> Reporter: Brian Williams
> Assignee: John Casey
> Fix For: 2.2-beta-2
>
>
> I attached my two assembly descriptors to the package phase, they get created
> correctly, but only the original JAR of my project gets deployed when I run
> "mvn deploy". Each of my descriptors makes a ZIP containing the JAR my
> project compiles plus other resources (don't ask me why they don't want them
> as part of the JAR).
> When I declared version 2.1 for the assembly plugin, my two assemblies
> deployed with my original JAR. This is the relevant section of my POM.xml:
> {{
> <artifactId>maven-assembly-plugin</artifactId>
> <version>2.1</version>
> <executions>
> <execution>
> <phase>package</phase>
> <configuration>
> <descriptors>
> <descriptor>assembly/windows.xml</descriptor>
> <descriptor>assembly/linux.xml</descriptor>
> </descriptors>
> </configuration>
> <goals><goal>assembly</goal></goals>
> </execution>
> </executions>
> }}
--
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
