You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Max Powers (JIRA)" <ji...@codehaus.org> on 2008/12/19 01:26:19 UTC
[jira] Created: (MNG-3922) Attaching classified artifacts not
working properly
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
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
[jira] Closed: (MSHADE-44) Attaching classified artifacts not
working properly
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSHADE-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann closed MSHADE-44.
-----------------------------------
Assignee: Benjamin Bentmann
Resolution: Fixed
Fix Version/s: 1.3
Fixed in [r729416|http://svn.eu.apache.org/viewvc?view=rev&revision=729416].
> Attaching classified artifacts not working properly
> ---------------------------------------------------
>
> Key: MSHADE-44
> URL: http://jira.codehaus.org/browse/MSHADE-44
> Project: Maven 2.x Shade Plugin
> Issue Type: Bug
> Affects Versions: 1.2
> Environment: windows
> Reporter: Max Powers
> Assignee: Benjamin Bentmann
> Fix For: 1.3
>
> Attachments: pom.xml, 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
[jira] Moved: (MSHADE-44) Attaching classified artifacts not
working properly
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSHADE-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann moved MNG-3922 to MSHADE-44:
----------------------------------------------
Affects Version/s: (was: 2.1.0-M1)
(was: 2.0.9)
1.2
Fix Version/s: (was: 2.1.0-M2)
(was: 2.0.10)
Key: MSHADE-44 (was: MNG-3922)
Project: Maven 2.x Shade Plugin (was: Maven 2)
> Attaching classified artifacts not working properly
> ---------------------------------------------------
>
> Key: MSHADE-44
> URL: http://jira.codehaus.org/browse/MSHADE-44
> Project: Maven 2.x Shade Plugin
> Issue Type: Bug
> Affects Versions: 1.2
> Environment: windows
> Reporter: Max Powers
> Attachments: pom.xml, 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
[jira] Commented: (MNG-3922) Attaching classified artifacts not
working properly
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (MNG-3922) Attaching classified artifacts not
working properly
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159060#action_159060 ]
Benjamin Bentmann commented on MNG-3922:
----------------------------------------
A workaround is to change the order of the plugins in the POMs, i.e. have the maven-sources-plugin (and other plugin that forks a lifecycle) execute after the maven-shade-plugin.
> 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
> Fix For: 2.0.10, 2.1.0-M2
>
> Attachments: pom.xml, 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
[jira] Issue Comment Edited: (MNG-3922) Attaching classified
artifacts not working properly
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158770#action_158770 ]
Benjamin Bentmann edited comment on MNG-3922 at 12/19/08 3:08 PM:
------------------------------------------------------------------
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)?
BTW, this POM also fails for with Maven 2.0.8, 2.0.7 and 2.0.6.
was (Author: bentmann):
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
[jira] Updated: (MNG-3922) Attaching classified artifacts not
working properly
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann updated MNG-3922:
-----------------------------------
Attachment: pom.xml
Attached a trimmed down POM to reproduce. As said, this fails for me with Maven 2.0.8, 2.0.7 and 2.0.6.
> 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
> Fix For: 2.0.10, 2.1.0-M2
>
> Attachments: pom.xml, 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
[jira] Updated: (MNG-3922) Attaching classified artifacts not
working properly
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MNG-3922:
------------------------------
Fix Version/s: 2.1.0-M2
2.0.10
not sure if this is intended to be fixed in 2.0.10 or 2.0.11, but dropping in here for now
> 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
> Fix For: 2.0.10, 2.1.0-M2
>
> 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
[jira] Updated: (MNG-3922) Attaching classified artifacts not
working properly
Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason van Zyl updated MNG-3922:
-------------------------------
Affects Version/s: 2.1.0-M1
> 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