karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Morgan Hautman (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (KARAF-3733) Update the repository.xml in a repository "on the fly"
Date Sat, 30 Jul 2016 07:12:20 GMT

    [ https://issues.apache.org/jira/browse/KARAF-3733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15400513#comment-15400513
] 

Morgan Hautman edited comment on KARAF-3733 at 7/30/16 7:11 AM:
----------------------------------------------------------------

What do you mean with "the update command already do that"?
The only thing the update command does is performing a scan:
caveRepository.scan();


Ok so a simple Thread is enough in a new command called {code} cave:repository-watcher {code}


was (Author: mhautman):
What do you mean with "the update command already do that"?
The only thing the update command does is performing a scan:
caveRepository.scan();


Ok so a simple Thread is enough in a new command called {code} cave:repository-watcher {code}.

> 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)

Mime
View raw message