[
http://jira.codehaus.org/browse/MRM-772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated MRM-772:
-----------------------------
Fix Version/s: 1.0.x
> metatadata-updater does not recognise deleted files when updating snapshot
> version metadata
> -------------------------------------------------------------------------------------------
>
> Key: MRM-772
> URL: http://jira.codehaus.org/browse/MRM-772
> Project: Archiva
> Issue Type: Improvement
> Components: repository scanning
> Affects Versions: 1.0.2
> Reporter: Jason Chaffee
> Priority: Critical
> Fix For: 1.0.x
>
>
> According to the documentation the metadata-updater will do the
> following:
> metadata-updater - Updates artifact metadata files depending on the content
> of the repository.
> I have been testing this by deploying several artifacts to the repository and
> getting a specific timestamp and build number in the maven-metatadata.xml
> file. Next, I delete the latest (snapshot) build from the repo, including
> checksums. I run the repository scanner and the database-updater and this
> file is never fixed based on the actual contents of the file system. Archive
> updates it internal metadata, but not maven's metadata and thus maven fails
> to download the artifact.
> From Brett:
> I think at present the updater corrects the <versions> flag, but not the
> snapshot information (it also doesn't correct the plugin group metadata).
--
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
