[
http://jira.codehaus.org/browse/MRM-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108417
]
Brett Porter commented on MRM-528:
----------------------------------
it seems like the best thing to do here is:
- wait until completion of any known batch of operations (eg, for purge,
collect a list of artifacts removed)
- for each consumer, execute beginScan; then for each file execute processFile;
then for each consumer execute completeScan
- rinse and repeat for database consumers
Things to check:
- fault tolerance of running consumers at the same time (in case a scheduled
scan occurs)
> just-in-time consumption of repository changes
> -----------------------------------------------
>
> Key: MRM-528
> URL: http://jira.codehaus.org/browse/MRM-528
> Project: Archiva
> Issue Type: Improvement
> Components: repository scanning
> Affects Versions: 1.0-beta-2
> Reporter: Brett Porter
>
> need to have a simple, reusable way to be able to trigger consumers for a
> given artifact just-in-time for things like addition via a proxy, removal via
> purge, etc.
--
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
