[ 
https://jira.codehaus.org/browse/MONE-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov closed MONE-5.
-----------------------------

    Resolution: Won't Fix

Please refer to 
https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014
 if you're wondering why this issue was closed out.

> M1 deploy blows away local repository metadata
> ----------------------------------------------
>
>                 Key: MONE-5
>                 URL: https://jira.codehaus.org/browse/MONE-5
>             Project: Maven One Plugin (RETIRED)
>          Issue Type: Bug
>    Affects Versions: 1.0
>            Reporter: Matthew Beermann
>            Priority: Blocker
>         Attachments: maven-metadata-apparch-snapshot.xml
>
>
> Steps to reproduce:
> 1) Bind maven-one-plugin:deploy-maven-one-repository to the "deploy" phase 
> (and add suitable configuration).
> 2) Run "mvn deploy" on a project
> 3) After the deploy finishes, look at maven-metadata.xml for the project in 
> the local repository.
> 4) Note that the file has been overwritten with invalid contents.
> In particular, the local repository metadata has been overwritten by the file 
> legacy_repo/${groupId}/poms/maven-metadata.xml. Unfortunately, because of the 
> way M1 repositories are structured, this file contains version numbers for 
> _all_ artifacts in the group. I'll attach mine in a moment as an example.
> This effectively corrupts the local repository. Subsequent builds that depend 
> on the affected project will fail because they're looking for phantom version 
> numbers that don't exist.
> Note: we recently switched to the WebDAV wagon for deployment, and this bug 
> seemed to show up at about the same time. The two could be related, or it 
> could just be a red herring...



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

Reply via email to