Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@karaf.apache.org
Date: Sat, 30 Jul 2016 07:12:20 +0000 (UTC)
From: "Morgan Hautman (JIRA)" <jira@apache.org>
To: issues@karaf.apache.org
Message-ID: <JIRA.12830784.1431974934000.176538.1469862740522@Atlassian.JIRA>
In-Reply-To: <JIRA.12830784.1431974934000@Atlassian.JIRA>
References: <JIRA.12830784.1431974934000@Atlassian.JIRA> <JIRA.12830784.1431974934665@arcas>
Subject: [jira] [Comment Edited] (KARAF-3733) Update the repository.xml in a
 repository "on the fly"
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Sat, 30 Jul 2016 07:12:22 -0000


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

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:reposit=
ory-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:reposit=
ory-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=C3=A9
>            Assignee: Jean-Baptiste Onofr=C3=A9
>             Fix For: cave-3.0.1, cave-4.0.1
>
>
> Right now, the only way to update the OBR metadata is by performing the s=
can 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 f=
or auto).


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)