[
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
