You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "John Casey (JIRA)" <ji...@codehaus.org> on 2005/06/09 20:22:10 UTC
[jira] Closed: (MRM-4) repoclean overwrites valid poms with dummy poms when there was none in m1 repo
[ http://jira.codehaus.org/browse/MRM-4?page=all ]
John Casey closed MRM-4:
------------------------
Resolution: Fixed
check before writing the generated pom to the target file, and ALWAYS attempt to verify/patch the checksums for the target pom.
> 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