Release and packaging management of OSGI projects is not so really easy
and rather complex. So I would like to avoid that cave brings more
complexicity (and uses others repositories) compare to what we have and
simplifies the work of the administrator. So cave should use what karaf
defines in etc config file
On 12/08/11 10:53, Jean-Baptiste Onofré wrote:
Hi Charles,
not for the moment, it's isolated repositories.
But we can add such kind of features.
I'm working on an import feature to be able to import a remote maven
repo into a local Cave repo.
Regards
JB
On 08/12/2011 10:50 AM, Charles Moulliard wrote:
Question : Does the cave repo uses the system local repo defined in
karaf/servicemix by default and also the repositories defined in
/etc/org.ops4j.pax.url.mvn.cfg file ?
On Fri, Aug 12, 2011 at 10:07 AM, Jean-Baptiste
Onofré<[email protected]> wrote:
Hi all,
you can find usage/screenshot preview about Apache Karaf Cave:
http://pastie.org/2360003
You can see (in this order):
- creation of a Cave repository (in the default Cave storage
location, using
filesystem backend
- list of Cave repositories
- upload of an artifact (from central maven repo) into the Cave repo
- register the Cave repository into the OBR RepositoryAdmin service
- creation/import of my local M2 repo, enable scan (to generate the
repository.xml) and register this repo in the OBR service at
creation time
- you can see with obr:list that we have all artifacts available
My TODO list is now to add JMX MBeans, REST API, features enterprise
repository.
Any comment/idea is welcome :)
Regards
JB
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
