You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@karaf.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2017/12/17 17:21:00 UTC

[jira] [Resolved] (KARAF-3733) Update the repository.xml in a repository "on the fly"

     [ https://issues.apache.org/jira/browse/KARAF-3733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Baptiste Onofré resolved KARAF-3733.
-----------------------------------------
       Resolution: Won't Fix
    Fix Version/s:     (was: cave-4.0.1)
                       (was: cave-3.0.1)

I think it's ok to use a static generation.

> 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é
>
> 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.4.14#64029)