You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2008/03/20 06:32:47 UTC
[jira] Assigned: (MRM-734) Unable to update metadata - No versions
found for reference
[ http://jira.codehaus.org/browse/MRM-734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter reassigned MRM-734:
--------------------------------
Assignee: Brett Porter
> Unable to update metadata - No versions found for reference
> ------------------------------------------------------------
>
> Key: MRM-734
> URL: http://jira.codehaus.org/browse/MRM-734
> Project: Archiva
> Issue Type: Bug
> Components: remote proxy
> Affects Versions: 1.0.1
> Reporter: James William Dumay
> Assignee: Brett Porter
> Fix For: 1.0.2
>
> Attachments: plugin metadata update fails.txt
>
>
> This occurs when requesting /org/apache/maven/plugins/maven-metadata.xml.
> The IOException is thrown updateMetadata because no artifact versions could be found in the maven-metadata.xml on merge.
> http://repo1.maven.org/maven2/activemq/activemq-gbean/maven-metadata.xml
> http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-metadata.xml
> The first file listed above is a plugin metadata file (it lists plugin prefix mappings) while the second lists the available artifact versions.
> MetadataTools.updateMetadata should be updated to handle plugin metadata files
> Exception report is attached.
--
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