[
https://issues.apache.org/jira/browse/KARAF-3733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15400502#comment-15400502
]
Morgan Hautman commented on KARAF-3733:
---------------------------------------
We have two solutions here:
1. Add options to the cave:repository-update command.
2. Make a new command cave:scan-repository that would kind of duplicate the
behavior of cave:repository-update.
I would choose for option 1, WDYT?
And can you also confirm that the scheduler should use Karaf's QuartzScheduler?
Thanks,
Morgan
> Update the repository.xml in a repository "on the fly"
> ------------------------------------------------------
>
> Key: KARAF-3733
> URL: https://issues.apache.org/jira/browse/KARAF-3733
> Project: Karaf
> Issue Type: Improvement
> Components: cave-server
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Fix For: cave-3.0.1, cave-4.0.1
>
>
> Right now, the only way to update the OBR metadata is by performing the scan
> command. Meaning that we need to execute the command each time that the
> repository is updated (adding/removing an artifact for instance).
> It makes sense to have a thread that periodically update the OBR metadata
> (that we can enable/disable with a command, like cave:scan-repository -a for
> auto).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
