Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id E1DA7200B56 for ; Sat, 30 Jul 2016 08:58:22 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id E092A160A8B; Sat, 30 Jul 2016 06:58:22 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 58139160A81 for ; Sat, 30 Jul 2016 08:58:22 +0200 (CEST) Received: (qmail 17088 invoked by uid 500); 30 Jul 2016 06:58:21 -0000 Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@karaf.apache.org Delivered-To: mailing list issues@karaf.apache.org Received: (qmail 17061 invoked by uid 99); 30 Jul 2016 06:58:21 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 30 Jul 2016 06:58:21 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 2C6332C0D61 for ; Sat, 30 Jul 2016 06:58:21 +0000 (UTC) Date: Sat, 30 Jul 2016 06:58:21 +0000 (UTC) From: "Morgan Hautman (JIRA)" To: issues@karaf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (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 X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Sat, 30 Jul 2016 06:58:23 -0000 [ https://issues.apache.org/jira/browse/KARAF-3733?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1540= 0502#comment-15400502 ]=20 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 QuartzSchedu= ler? 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=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)