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 2010/09/23 17:17:33 UTC
[jira] Closed: (MASSEMBLY-370) Run assembly 2 times to create 2
assemblies
[ http://jira.codehaus.org/browse/MASSEMBLY-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Casey closed MASSEMBLY-370.
--------------------------------
Resolution: Not A Bug
Assignee: John Casey
you should have no problem accomplishing this using the assembly:single mojo, perhaps in combination with the attachmentClassifier setting of the dependencySet.
> Run assembly 2 times to create 2 assemblies
> -------------------------------------------
>
> Key: MASSEMBLY-370
> URL: http://jira.codehaus.org/browse/MASSEMBLY-370
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-2
> Environment: linux/maven 2.0.9
> Reporter: Luc Willems
> Assignee: John Casey
>
> I like to create 2 additional assemblies :
> - a JAR assembly with all source/javadocs/dependency jars used to distribute to client
> - a WAR assembly to create a overlay war to use in a webapp
> setup is as follow :
> - configuring the maven assembly plugin 2 times in build section , with different execution id , using single goal
> - use different descriptor pointing to 2 different assembly xml files
> - run package
> the second execution will not use the second assembly description file but is fix on the first. so the first
> assembly is build twice
--
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