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 18:23:33 UTC
[jira] Closed: (MASSEMBLY-204) Make a single goal
(assembly:assembly) that covers all cases of assembly:attached, directory,
...
[ http://jira.codehaus.org/browse/MASSEMBLY-204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Casey closed MASSEMBLY-204.
--------------------------------
Resolution: Fixed
Fix Version/s: (was: 2.3-beta-1)
2.2-beta-6
Assignee: John Casey
assembly:single is that mojo. All others are deprecated. For directory assemblies, use <format>dir</format> in the assembly descriptor.
> Make a single goal (assembly:assembly) that covers all cases of assembly:attached, directory, ...
> -------------------------------------------------------------------------------------------------
>
> Key: MASSEMBLY-204
> URL: http://jira.codehaus.org/browse/MASSEMBLY-204
> Project: Maven 2.x Assembly Plugin
> Issue Type: Improvement
> Affects Versions: 2.2-beta-1
> Reporter: Geoffrey De Smet
> Assignee: John Casey
> Fix For: 2.2-beta-6
>
>
> It shouldn't be that hard to check wheter it's a multiproject or not.
> From a users perspective, when I bind the assembly plugin like this:
> <plugin>
> <artifactId>maven-assembly-plugin</artifactId>
> <executions>
> <execution>
> <goals>
> <goal>assembly</goal>
> </goals>
> </execution>
> it should just work, without having to figure out if it's a multiproject, etc.
> Ps: I 've read the 7 different assembly goals 5 times, and I only understand the difference between unpack, attached and assembly...
> Great improvements in 2.2's descriptor though :)
--
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