[
http://jira.codehaus.org/browse/MRM-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=211194#action_211194
]
Brett Porter commented on MRM-999:
----------------------------------
what we want here:
- an event triggered when something in the system (eg webdav) deletes, or
detects the deletion of, a file
- behaviour for handling out related files should be deleted (or if we rely on
whatever is deleting to do it as well)
- clean up of metadata associated with the file
Remember the use cases
- if the content is on a separate server to the metadata
we need to add a new scanning service for doing these kind of "repairs", if it
is done outside the web application, though for now we can attach it to the end
of the main repository scan
> After artifact removal the database does not update
> ---------------------------------------------------
>
> Key: MRM-999
> URL: http://jira.codehaus.org/browse/MRM-999
> Project: Archiva
> Issue Type: Bug
> Affects Versions: 1.1.2
> Environment: unix
> Reporter: Sonia L
> Fix For: 1.4
>
>
> Removed an artifact from the file system, then I went into
> Administration/Database and clicked on "Update Database now", I did it a few
> times, but the groupId/artifactId are still there !!!!
> See http://www.nabble.com/How-to-remove-an-artifact-td15005386.html for more
> details
--
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
