maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "SebbASF (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MASSEMBLY-553) Assembly plugin ignores attached assemblies
Date Thu, 31 Mar 2011 10:50:22 GMT

    [ http://jira.codehaus.org/browse/MASSEMBLY-553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=262070#action_262070
] 

SebbASF commented on MASSEMBLY-553:
-----------------------------------

We just discovered that 2.2[.1] work if the clean or package goals are run before install.

It seems to be an inheritance issue, because 2.2.1 works fine if I add the execution goal
single to the test POM, either directly under the build section or in a separate profile.


It does not work if the goal is only in the parent profile.

That surely is not intentional?


> Assembly plugin ignores attached assemblies
> -------------------------------------------
>
>                 Key: MASSEMBLY-553
>                 URL: http://jira.codehaus.org/browse/MASSEMBLY-553
>             Project: Maven 2.x Assembly Plugin
>          Issue Type: Bug
>    Affects Versions: 2.2, 2.2.1
>            Reporter: SebbASF
>            Priority: Critical
>         Attachments: assembly-bug.zip
>
>
> This used to work in 2.2-beta-5, but both 2.2 and 2.2.1 seem to ignore attached descriptors
in "mvn install"
> Sample project to follow.
> This works:
> mvn -Dass.vers=2.2-beta-5 install -Prc
> This does not:
> mvn -Dass.vers=2.2.1 install -Prc
> If you compare the ouput from the two runs, you will see that the following is missing
from 2.2.1:
> [INFO] [assembly:attached {execution: default}]
> [INFO] Reading assembly descriptor: src/assembly/bin.xml
> [INFO] Reading assembly descriptor: src/assembly/src.xml
> [INFO] Building zip: D:\maven-tests\assembly-bug\target\assembly-bug-1.0-SNAPSHOT-bin.zip
> [INFO] Building zip: D:\maven-tests\assembly-bug\target\assembly-bug-1.0-SNAPSHOT-src.zip
> Apache Commons cannot use 2.2 or 2.2.1 as a result of this bug

-- 
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

        

Mime
View raw message