[
http://jira.codehaus.org/browse/MNG-3415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126548
]
John Casey commented on MNG-3415:
---------------------------------
I have the fix in place on my localhost, but I'm still trying to nail down the
integration tests and make them work in both 2.0.9 and 2.1. It'll be Monday
before I get this sorted out.
> Transfer errors cause junk metadata in the local repo
> -----------------------------------------------------
>
> Key: MNG-3415
> URL: http://jira.codehaus.org/browse/MNG-3415
> Project: Maven 2
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 2.0.8
> Reporter: Brian Fox
> Assignee: John Casey
> Fix For: 2.0.9
>
> Attachments: MNG-3415.diff
>
>
> I see this all the time and I swear there was an issue for it, but now I
> can't find it. Sometimes there is metadata in the repo, usually after an
> offline build or a build where something went wrong downloading artifacts.
> Maven will apparently decide based on the metadata that the file can never be
> found and will simply fail on a missing artifact. You can tell this has
> happened because no attempt has actually been made to download the artifact
> from a repository. Subsequent clearing of (portions) the localrepo fixes the
> issue. This is terribly confusing to new users...and annoying to everyone.
--
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
