[
http://jira.codehaus.org/browse/MNG-3922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158770#action_158770
]
Benjamin Bentmann commented on MNG-3922:
----------------------------------------
Story goes like this: The build calls both {{source:jar}} and {{shade:shade}},
in that order.The Sources Plugin forks a lifecycle and creates an execution
project for the current project. The execution project survives the execution
of {{source:jar}} and is still present in the main {{MavenProject}} instance
when {{shade:shade}} is executed. And the Shade Plugin attaches its artifacts
to the execution project, not the main project instance. However, only the
artifacts of the main project are installed/deployed.
So:
a) Is it intended that the execution project survives the execution of the mojo
which caused the forked lifecycle?
b) Why does the Shade Plugin bother to use the execution project (if existent)?
> Attaching classified artifacts not working properly
> ---------------------------------------------------
>
> Key: MNG-3922
> URL: http://jira.codehaus.org/browse/MNG-3922
> Project: Maven 2
> Issue Type: Bug
> Affects Versions: 2.0.9, 2.1.0-M1
> Environment: windows
> Reporter: Max Powers
> Attachments: pom.xml
>
>
> We are using the shade plugin to build a couple of cli classifier artifacts
> for the nexus-indexer, however, these artifacts aren't attached properly in
> mvn 2.0.9 (or the 2.0.10-RC5). They do get attached properly in mvn 2.0.8
> and mvn 3.x.
> I have attached the pom file where we are using the shade plugin to build 2
> seperate attached classifier artifacts.
--
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
