[
http://jira.codehaus.org/browse/MRM-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=154899#action_154899
]
Duncan Doyle commented on MRM-999:
----------------------------------
I've got the same problem with Archiva 1.1.3.
Another strange issue, which is probably related to this one, is that purged
snapshots (I only keep 2 of them) are still returned when doing a 'search'
(they are not present on the filesystem), but are not visible when browsing the
repository (which is expected). The files I've removed myself (via the
filesystem) however are still visible both when searching and browsing, even
after scanning the repository and updating the database.
The cron scheduled database-job doesn't clean the repository either by the way.
> 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
>
> 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
