yes, of course, thanks! However, on that page, all consumers are enabled: -not-present-remove-indexed -not-present-remove-db-artifact -not-present-remove-db-project
Any idea why the entries are not removed from the database? In the log, I can see entries for the ArchivaRepositoryScanningTaskExecutor, resulting in a detailed statistics overview. However I cannot see any statistics for the ArchivaDatabaseUpdateTaskExecutor. Could it be that for some reason the ArchivaDatabaseUpdateTaskExecutor is triggered, but not executed? The cron definition is "0 0 * * * ?" (default) Maria Odea Ching-5 wrote: > > Oh, it's not in the Repository Scanning page. You should be able to see it > by clicking Database from the menu. The Database page should show the > consumers attached to the db scanning, including the cleanup consumers :) > > Thanks, > Deng > > On Tue, Apr 7, 2009 at 6:52 PM, Marc Lustig <m...@marclustig.com> wrote: > >> >> I cannot find any consumer section "Database - Artifact Cleanup >> Scanning". >> We have sections >> "Repository Scanning - Consumers of Known Content " >> ->all enabled >> >> "Repository Scanning - Consumers of Invalid Content" >> -> no consumer existing >> >> We are running Archiva 1.1.3 >> Do we have to add additional consumers? How to do that? >> >> thanks >> Marc >> >> >> >> >> Maria Odea Ching-5 wrote: >> > >> > Hi Marc, >> > >> > I think there are some consumers which already do this.. You should be >> > able >> > to see them in the Database page (Database - Artifact Cleanup Scanning >> > section). They should be enabled by default and executed during >> database >> > scanning. Were you able to check if these were enabled in your Archiva >> > instance? >> > >> > Thanks, >> > Deng >> > >> > On Tue, Apr 7, 2009 at 5:36 PM, Marc Lustig <m...@marclustig.com> wrote: >> > >> >> >> >> We often need to remove artifacts manually. We do this by deleting the >> >> files >> >> from the managed-repo on the fs. >> >> Unfortunately, those files are not automativally removed from the >> >> database. >> >> >> >> Is there any fix for this available? >> >> >> >> If not, I propose to implement a new consumer "auto-remove artifacts >> from >> >> the database" in case files where deleted from the fs. >> >> >> >> -- >> >> View this message in context: >> >> >> http://www.nabble.com/consumer-to-auto-remove-artifact-from-DB-tp22925611p22925611.html >> >> Sent from the archiva-users mailing list archive at Nabble.com. >> >> >> >> >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/consumer-to-auto-remove-artifact-from-DB-tp22925611p22926610.html >> Sent from the archiva-users mailing list archive at Nabble.com. >> >> > > -- View this message in context: http://www.nabble.com/consumer-to-auto-remove-artifact-from-DB-tp22925611p22927284.html Sent from the archiva-users mailing list archive at Nabble.com.
