[jira] Commented: (MRM-4) repoclean overwrites valid poms with dummy poms when there was none in m1 repo

["John Casey (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/MRM-4?page=comments#action_40823 ]
     
John Casey commented on MRM-4:
------------------------------

shouldn't we opt to publish to the m1 repo and let the converter push it across instead of putting in this check? We talked about this at one time on IRC...

One thing: for m2 devs, the lag time involved in this push-and-convert process may be too much...perhaps we need to figure out an easy way to trigger priority conversions when such artifacts are deployed...? Just an idea.

> repoclean overwrites valid poms with dummy poms when there was none in m1 repo
> ------------------------------------------------------------------------------
>
>          Key: MRM-4
>          URL: http://jira.codehaus.org/browse/MRM-4
>      Project: Maven Repository Manager
>         Type: Bug
>   Components: repository-converter
>     Reporter: Brett Porter
>     Assignee: John Casey

>
>
> I copied the wagon JARs from the m2 repo to the m1 repo so that m1 users could access them. However, repoclean detected they were newer and "converted" them, copying the JARs back to the original location where they already resided, and overwriting valid m2 poms with dummy groupId/artifactId only POMs because there were none in the m1 repo.

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