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 2014/06/30 14:54:25 UTC

[jira] [Resolved] (KARAF-1027) Have cave:update-repository work with proxy repositories

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

Jean-Baptiste Onofré resolved KARAF-1027.
-----------------------------------------

    Resolution: Won't Fix

> 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.1, cave-3.0.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 file.



--
This message was sent by Atlassian JIRA
(v6.2#6252)