You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "James William Dumay (JIRA)" <ji...@codehaus.org> on 2007/08/16 05:57:48 UTC
[jira] Created: (MNG-3151) Allow plugins that attach artifacts to
specify deployment locations
Allow plugins that attach artifacts to specify deployment locations
-------------------------------------------------------------------
Key: MNG-3151
URL: http://jira.codehaus.org/browse/MNG-3151
Project: Maven 2
Issue Type: Improvement
Components: Artifacts and Repositories, General
Affects Versions: 2.0.8
Reporter: James William Dumay
The following patch allows plugins to specify Distribution Management relating to their attached artifacts.
This is useful in large Java shops where, depending on the type of artifact (Javadoc, source, assembly, etc)m you may want to deploy these artifacts to different repositories (eg public and private).
--
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-3151) Allow plugins that attach artifacts to
specify deployment locations
Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105291 ]
Maria Odea Ching commented on MNG-3151:
---------------------------------------
I got test failures from DefaultMavenProjectHelperTest due to NPEs in AttachedArtifact.getVersion() so the patch wasn't applied. Also, the patch needs to be updated to trunk. Thanks!
> Allow plugins that attach artifacts to specify deployment locations
> -------------------------------------------------------------------
>
> Key: MNG-3151
> URL: http://jira.codehaus.org/browse/MNG-3151
> Project: Maven 2
> Issue Type: Improvement
> Components: Artifacts and Repositories, General
> Affects Versions: 2.0.8
> Reporter: James William Dumay
> Assignee: Brett Porter
> Fix For: 2.0.8
>
> Attachments: MNG-3151-maven-2.0.x.patch
>
>
> The following patch allows plugins to specify Distribution Management relating to their attached artifacts.
> This is useful in large Java shops where, depending on the type of artifact (Javadoc, source, assembly, etc)m you may want to deploy these artifacts to different repositories (eg public and private).
--
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-3151) Allow plugins that attach artifacts to
specify deployment locations
Posted by "Foo Fers (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=181070#action_181070 ]
Foo Fers commented on MNG-3151:
-------------------------------
Get off your high horse van Zyl and stop spruking Nexus in this forum.
> Allow plugins that attach artifacts to specify deployment locations
> -------------------------------------------------------------------
>
> Key: MNG-3151
> URL: http://jira.codehaus.org/browse/MNG-3151
> Project: Maven 2
> Issue Type: Improvement
> Components: Artifacts and Repositories, General
> Affects Versions: 2.0.8
> Reporter: James William Dumay
> Fix For: 2.2.x
>
> Attachments: MNG-3151-maven-2.0.x.patch, MNG-3151-maven-2.1.x.patch
>
>
> The following patch allows plugins to specify Distribution Management relating to their attached artifacts.
> This is useful in large Java shops where, depending on the type of artifact (Javadoc, source, assembly, etc)m you may want to deploy these artifacts to different repositories (eg public and private).
--
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-3151) Allow plugins that attach artifacts to
specify deployment locations
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MNG-3151:
------------------------------
Patch Submitted: (was: [Yes])
> Allow plugins that attach artifacts to specify deployment locations
> -------------------------------------------------------------------
>
> Key: MNG-3151
> URL: http://jira.codehaus.org/browse/MNG-3151
> Project: Maven 2
> Issue Type: Improvement
> Components: Artifacts and Repositories, General
> Affects Versions: 2.0.8
> Reporter: James William Dumay
> Fix For: 2.0.x
>
> Attachments: MNG-3151-maven-2.0.x.patch, MNG-3151-maven-2.1.x.patch
>
>
> The following patch allows plugins to specify Distribution Management relating to their attached artifacts.
> This is useful in large Java shops where, depending on the type of artifact (Javadoc, source, assembly, etc)m you may want to deploy these artifacts to different repositories (eg public and private).
--
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-3151) Allow plugins that attach artifacts to
specify deployment locations
Posted by "James William Dumay (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James William Dumay updated MNG-3151:
-------------------------------------
Attachment: MNG-3151-maven-2.0.x.patch
Patch contains functional implementation of this issue.
The Artifact setRepository() and getRepository() have had their usage changed so that depending on the context of their use, they are either the ArtifactRepository that they originate from (eg, dependency) or where their destination will be when the Artifact is deployed.
> Allow plugins that attach artifacts to specify deployment locations
> -------------------------------------------------------------------
>
> Key: MNG-3151
> URL: http://jira.codehaus.org/browse/MNG-3151
> Project: Maven 2
> Issue Type: Improvement
> Components: Artifacts and Repositories, General
> Affects Versions: 2.0.8
> Reporter: James William Dumay
> Attachments: MNG-3151-maven-2.0.x.patch
>
>
> The following patch allows plugins to specify Distribution Management relating to their attached artifacts.
> This is useful in large Java shops where, depending on the type of artifact (Javadoc, source, assembly, etc)m you may want to deploy these artifacts to different repositories (eg public and private).
--
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: (MNG-3151) Allow plugins that attach artifacts to
specify deployment locations
Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason van Zyl closed MNG-3151.
------------------------------
Resolution: Won't Fix
This is just such a bad idea. We can't compensate for poor internal infrastructure. It's easy to separate logical views using Apache rewrite rules, or a repository manager. I doubt anyone will convince me this is a actually a good idea. How, for example, would the IDE integration get the sources or javadocs for a particular artifact if these were all deployed in different locations? Then this would involve yet another mapping to unify all the attached artifacts. It's just a rat hole. -1.
> Allow plugins that attach artifacts to specify deployment locations
> -------------------------------------------------------------------
>
> Key: MNG-3151
> URL: http://jira.codehaus.org/browse/MNG-3151
> Project: Maven 2
> Issue Type: Improvement
> Components: Artifacts and Repositories, General
> Affects Versions: 2.0.8
> Reporter: James William Dumay
> Fix For: 2.2.x
>
> Attachments: MNG-3151-maven-2.0.x.patch, MNG-3151-maven-2.1.x.patch
>
>
> The following patch allows plugins to specify Distribution Management relating to their attached artifacts.
> This is useful in large Java shops where, depending on the type of artifact (Javadoc, source, assembly, etc)m you may want to deploy these artifacts to different repositories (eg public and private).
--
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-3151) Allow plugins that attach artifacts to
specify deployment locations
Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=181095#action_181095 ]
Jason van Zyl commented on MNG-3151:
------------------------------------
Has nothing to do with Nexus really, the idea is just flawed because it creates a disconnection between primary artifact and its secondary artifacts. But this is a perfect case where an organization that has a requirement for this can maintain these patches themselves and then the support costs are where they belong. These patches are really not generally useful.
This feature being implemented generally would be generally harmful. This will not be implemented in Maven, at least in this form, as it doesn't provide a working solution for client code to function in the same way that it does now. These patches handle the the case for the deployment but says nothing about the consumption especially where all IDE integration and many IDE related plugins rely on being able to calculate the location of secondary artifacts based on the primary artifact.
> Allow plugins that attach artifacts to specify deployment locations
> -------------------------------------------------------------------
>
> Key: MNG-3151
> URL: http://jira.codehaus.org/browse/MNG-3151
> Project: Maven 2
> Issue Type: Improvement
> Components: Artifacts and Repositories, General
> Affects Versions: 2.0.8
> Reporter: James William Dumay
> Fix For: 2.2.x
>
> Attachments: MNG-3151-maven-2.0.x.patch, MNG-3151-maven-2.1.x.patch
>
>
> The following patch allows plugins to specify Distribution Management relating to their attached artifacts.
> This is useful in large Java shops where, depending on the type of artifact (Javadoc, source, assembly, etc)m you may want to deploy these artifacts to different repositories (eg public and private).
--
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-3151) Allow plugins that attach artifacts to
specify deployment locations
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MNG-3151:
------------------------------
Fix Version/s: (was: 2.0.8)
2.0.x
Not applied following objections on dev@maven.apache.org list.
If you need this feature, or have a similar use case that could help build a solution - please comment and vote for it.
> Allow plugins that attach artifacts to specify deployment locations
> -------------------------------------------------------------------
>
> Key: MNG-3151
> URL: http://jira.codehaus.org/browse/MNG-3151
> Project: Maven 2
> Issue Type: Improvement
> Components: Artifacts and Repositories, General
> Affects Versions: 2.0.8
> Reporter: James William Dumay
> Fix For: 2.0.x
>
> Attachments: MNG-3151-maven-2.0.x.patch, MNG-3151-maven-2.1.x.patch
>
>
> The following patch allows plugins to specify Distribution Management relating to their attached artifacts.
> This is useful in large Java shops where, depending on the type of artifact (Javadoc, source, assembly, etc)m you may want to deploy these artifacts to different repositories (eg public and private).
--
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-3151) Allow plugins that attach artifacts to
specify deployment locations
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MNG-3151:
------------------------------
Fix Version/s: (was: 2.2.x)
> Allow plugins that attach artifacts to specify deployment locations
> -------------------------------------------------------------------
>
> Key: MNG-3151
> URL: http://jira.codehaus.org/browse/MNG-3151
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Artifacts and Repositories, General
> Affects Versions: 2.0.8
> Reporter: James William Dumay
> Attachments: MNG-3151-maven-2.0.x.patch, MNG-3151-maven-2.1.x.patch
>
>
> The following patch allows plugins to specify Distribution Management relating to their attached artifacts.
> This is useful in large Java shops where, depending on the type of artifact (Javadoc, source, assembly, etc)m you may want to deploy these artifacts to different repositories (eg public and private).
--
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-3151) Allow plugins that attach artifacts to
specify deployment locations
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MNG-3151:
------------------------------
Fix Version/s: 2.0.8
Patch Submitted: [Yes]
I took a look at this yesterday and it seems like the right way to go. Will take another look and apply shortly.
> Allow plugins that attach artifacts to specify deployment locations
> -------------------------------------------------------------------
>
> Key: MNG-3151
> URL: http://jira.codehaus.org/browse/MNG-3151
> Project: Maven 2
> Issue Type: Improvement
> Components: Artifacts and Repositories, General
> Affects Versions: 2.0.8
> Reporter: James William Dumay
> Assignee: Brett Porter
> Fix For: 2.0.8
>
> Attachments: MNG-3151-maven-2.0.x.patch
>
>
> The following patch allows plugins to specify Distribution Management relating to their attached artifacts.
> This is useful in large Java shops where, depending on the type of artifact (Javadoc, source, assembly, etc)m you may want to deploy these artifacts to different repositories (eg public and private).
--
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-3151) Allow plugins that attach artifacts to
specify deployment locations
Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105339 ]
Jason van Zyl commented on MNG-3151:
------------------------------------
I'm not sure this is really something we want to encourage. Why would you want to separate the javadoc, and sources from the original artifact?
> Allow plugins that attach artifacts to specify deployment locations
> -------------------------------------------------------------------
>
> Key: MNG-3151
> URL: http://jira.codehaus.org/browse/MNG-3151
> Project: Maven 2
> Issue Type: Improvement
> Components: Artifacts and Repositories, General
> Affects Versions: 2.0.8
> Reporter: James William Dumay
> Assignee: Brett Porter
> Fix For: 2.0.8
>
> Attachments: MNG-3151-maven-2.0.x.patch
>
>
> The following patch allows plugins to specify Distribution Management relating to their attached artifacts.
> This is useful in large Java shops where, depending on the type of artifact (Javadoc, source, assembly, etc)m you may want to deploy these artifacts to different repositories (eg public and private).
--
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-3151) Allow plugins that attach artifacts to
specify deployment locations
Posted by "James William Dumay (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James William Dumay updated MNG-3151:
-------------------------------------
Attachment: MNG-3151-maven-2.1.x.patch
Adding patch for trunk.
> Allow plugins that attach artifacts to specify deployment locations
> -------------------------------------------------------------------
>
> Key: MNG-3151
> URL: http://jira.codehaus.org/browse/MNG-3151
> Project: Maven 2
> Issue Type: Improvement
> Components: Artifacts and Repositories, General
> Affects Versions: 2.0.8
> Reporter: James William Dumay
> Assignee: Brett Porter
> Fix For: 2.0.8
>
> Attachments: MNG-3151-maven-2.0.x.patch, MNG-3151-maven-2.1.x.patch
>
>
> The following patch allows plugins to specify Distribution Management relating to their attached artifacts.
> This is useful in large Java shops where, depending on the type of artifact (Javadoc, source, assembly, etc)m you may want to deploy these artifacts to different repositories (eg public and private).
--
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