[ http://jira.codehaus.org/browse/MASSEMBLY-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Albert Kurucz updated MASSEMBLY-521: ------------------------------------ Attachment: src.xml distribution.xml {code:xml} <plugin> <artifactId>maven-assembly-plugin</artifactId> <version>2.2</version> <configuration> <descriptors> <descriptor>src/assemblies/distribution.xml</descriptor> <descriptor>src/assemblies/src.xml</descriptor> </descriptors> </configuration> <executions> <execution> <id>package-single</id> <phase>package</phase> <goals> <goal>attached</goal> </goals> </execution> </executions> </plugin> {code} If you replace the 'attached' goal to 'single', then only the distribution ZIP file is attached, but the src ZIP file is missing. > Un-depricate the 'attached' goal > -------------------------------- > > Key: MASSEMBLY-521 > URL: http://jira.codehaus.org/browse/MASSEMBLY-521 > Project: Maven 2.x Assembly Plugin > Issue Type: New Feature > Affects Versions: 2.2 > Reporter: Albert Kurucz > Attachments: distribution.xml, src.xml > > > I need to provide two assembly files of the same artifact, because of some > requirements from my project's consumers. The 'attached' goal serves me well, > and I don't see why it should "wreak havoc with normal build process". > However, because the goal is "DEPRECATED", I am trying to find alternative > solution. > Please explain how I could easily attach two assembly files without the > 'attached' goal. > Because of the instructions on the maven-assembly-plugin web site "Use > assembly:single instead!", I have tried it, but the 'single' goal failed to > deliver. (My second assembly was not attached). -- 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