[
http://jira.codehaus.org/browse/MRM-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maria Odea Ching closed MRM-37.
-------------------------------
Resolution: Fixed
Fixed in -r584735
These were the changes made:
- added code for cleaning up the database of artifacts that are no longer
existing in the repository
(DatabaseCleanupRemoveArtifactConsumer and DatabaseCleanupRemoveProjectConsumer)
- created tests for database cleanup of removed artifacts
- updated some of the test cases (in archiva-database and archiva-scheduled
modules) to reflect the changes in thedb cleanup consumers
The cleaning up of the index was not yet included here as i suspect the locking
problem (same as with the repository purge) will occur. I'll open a separate
jira for this.
Thanks!
> discover the deletion of artifacts
> ----------------------------------
>
> Key: MRM-37
> URL: http://jira.codehaus.org/browse/MRM-37
> Project: Archiva
> Issue Type: Improvement
> Components: repository scanning
> Reporter: Brett Porter
> Assignee: Maria Odea Ching
> Fix For: 1.0-beta-3
>
>
> currently, the discovery mechanism is geared to walking a source repository
> and insert into the target repository. However, there is no way to determine
> if an artifact has been removed. We may need to track this - potentially
> using metadata or the repository index.
--
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
