You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Albert Kurucz (JIRA)" <ji...@codehaus.org> on 2010/10/29 18:39:05 UTC
[jira] Created: (MASSEMBLY-521) Un-depricate the 'attached' goal
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
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
[jira] Updated: (MASSEMBLY-521) Un-depricate the 'attached' goal
Posted by "Albert Kurucz (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (MASSEMBLY-521) Un-depricate the 'attached' goal
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=241618#action_241618 ]
John Casey commented on MASSEMBLY-521:
--------------------------------------
If you can, please provide a sample project where the attachment step is failing when using the assembly:single goal. I haven't run into any cases where attachment doesn't work.
I think the better all-around solution is to get the assembly:single goal working properly in this use case, rather than bringing back the attached goal (which causes all sorts of problems by virtue of being an aggregator mojo).
> 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
>
> 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
[jira] Updated: (MASSEMBLY-521) Some assemblies NOT attached when
using multiple assemblies in one execution
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Casey updated MASSEMBLY-521:
---------------------------------
Summary: Some assemblies NOT attached when using multiple assemblies in one execution (was: Un-depricate the 'attached' goal)
This isn't a problem with the single goal vs the attached goal, unless there is a bug in the way multiple descriptors' output is handled (read: attached).
In other words, the solution isn't to undeprecate the mess that is the 'assembly:attached' goal. Rather, the solution is to figure out whether/why the attachments for multiple descriptors in one execution are failing somehow in the 'assembly:single' goal, and fix that.
> Some assemblies NOT attached when using multiple assemblies in one execution
> ----------------------------------------------------------------------------
>
> 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