[ http://jira.codehaus.org/browse/MRM-4?page=comments#action_40839 ] Brett Porter commented on MRM-4: --------------------------------
I think the proper solution is to publish to m2 and convert back to m1 - but you indicated that would be quite a bit harder as it is currently only design to run over an m1 repo. I think this is still a bug. Publishing to m1 with no POM should not get rid of valid info in the m2 repo. > 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
