karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré (JIRA) <j...@apache.org>
Subject [jira] [Work started] (KARAF-1027) Have cave:update-repository work with proxy repositories
Date Wed, 14 Aug 2013 01:15:47 GMT

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

Work on KARAF-1027 started by Jean-Baptiste Onofré.

> Have cave:update-repository work with proxy repositories
> --------------------------------------------------------
>                 Key: KARAF-1027
>                 URL: https://issues.apache.org/jira/browse/KARAF-1027
>             Project: Karaf
>          Issue Type: Improvement
>          Components: cave-repository
>    Affects Versions: cave-2.3.0
>            Reporter: Glen Mazza
>            Assignee: Jean-Baptiste Onofré
>             Fix For: cave-2.3.0
>         Attachments: proxyupdate.patch
> Supplied patch makes following changes:
> 1.) cave:proxy-repository now creates the repository before populating its repository.xml
with the remote repository's contents (prior functionality would raise an exception if the
repository did not exist.)
> 2.) switches the "non-register" to OBR option from -nu to -nr (like create repository)
> 3.) Like create-repository, will raise an exception if the proxy repository already exists.
> 4.) Adds a proxiedurl attribute to the repository.xml file (for subsequent reading when
loading an already created proxy repository--functionality is not yet used.)  Warning: the
schema for the repository.xml now deviates from Felix because of this additional attribute
(unsure if that matters), although it still loads into the Karaf OBR (obr:listurl).
> 5.) cave:update-repository will now work for both normal and proxied cave repositories,
in the latter case it does a rescan of the remote repository and recreates the repository.xml

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message