I think you misunderstood JB. He wasn't talking about providing the artifacts afaik. But yeah, if you want to avoid each karaf instance going to maven central you could deploy a nexus and change the etc/org.ops4j.pax.url.mvn.cfg config to point to it
On Wed, Mar 16, 2011 at 08:07, Charles Moulliard <cmoulli...@gmail.com> wrote: > Hi JB, > > What you propose looks like a nexus - sonatype repository management > platform for Karaf. Do we need that ? What could be the benefit to use > JNDI or LDAP to find features/bundles ? > > Regards, > > Charles > > On Fri, Mar 11, 2011 at 5:41 PM, <j...@nanthrax.net> wrote: >> Hi guys, >> >> Correct me if I'm wrong but, currently, we have an OBR into Karaf. >> >> I wonder if it could be interesting to extend this OBR in a more enterprise >> oriented way (as an optional feature) with: >> - RESTful service to administrate the repo and upload/download bundle >> - support of kar and features descriptor >> - JNDI lookup support >> - LDAP lookup support >> - management/extension of the existing obr page in the web console >> >> I don't know if we need to implement by ourself or embed an existing project >> (felix bundlerepository/ace, archiva, aries obr, others ?). >> >> Anyway I think it could be interesting to turn Karaf into an EBR supporting >> remoting, management, etc. >> >> Wdyt ? >> >> Regards >> JB >> > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
