You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jason van Zyl (JIRA)" <ji...@codehaus.org> on 2007/11/04 08:14:10 UTC
[jira] Updated: (MNG-2963) Do not update metadata unless the
artifact actually made it down
[ http://jira.codehaus.org/browse/MNG-2963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason van Zyl updated MNG-2963:
-------------------------------
Fix Version/s: (was: 2.0.9)
2.1-alpha-1
I'm going to fix this in Maven Artifact and we can decide to use that in 2.0.9 for the fix.
> Do not update metadata unless the artifact actually made it down
> ----------------------------------------------------------------
>
> Key: MNG-2963
> URL: http://jira.codehaus.org/browse/MNG-2963
> Project: Maven 2
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 2.0.x
> Reporter: Jason van Zyl
> Assignee: Jason van Zyl
> Fix For: 2.1-alpha-1
>
>
> We can also have a secondary check to see that if a metadata file contains no valid versions to nuke it and try to download a valid one. This will correct anything left over from previous versions of Maven.
--
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