You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2005/11/24 08:18:06 UTC

[jira] Updated: (MRM-13) utilise repository relocation information during conversion of an artifact

     [ http://jira.codehaus.org/browse/MRM-13?page=all ]

Brett Porter updated MRM-13:
----------------------------

    Fix Version: 1.0

> utilise repository relocation information during conversion of an artifact
> --------------------------------------------------------------------------
>
>          Key: MRM-13
>          URL: http://jira.codehaus.org/browse/MRM-13
>      Project: Maven Repository Manager
>         Type: New Feature
>   Components: repository-converter
>     Reporter: Brett Porter
>      Fix For: 1.0

>
>
> we should allow some extra metdata in the m1 pom that can be recognised as relocation information:
> <properties>
>   <relocated.groupId />
>   <relocated.artifactId />
>   <relocated.version />
>   <relocated.message />
> </properties>
> when encountering this, the converted POM and JAR will go to the new location in the m2 repository, and the marker POM (just the relocation information) should go to the old location (and any artifact there should be removed)
> This would allow us to move Jakarta commons en mass to the dotted groupId layout for example.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org