[jira] Closed: (MNG-3151) Allow plugins that attach artifacts to specify deployment locations

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