My concern is to deploy clients JARs like by example JARS used by project Apache Hadoop
2011/1/11 Adrian Trenaman <[email protected]> > I *think* Charles's original suggestion was concerning client JARs, rather > than bundles? > > @Charles: can you clarify? > > > On 11/01/2011 09:58, Łukasz Dywicki wrote: > >> You may specify additional "repository" for Karaf. You may do that by >> "bundle.locations" property in config.properties. >> >> Best regards, >> Lukasz >> >> -----Original Message----- >> From: Adrian Trenaman [mailto:[email protected]] >> Sent: Tuesday, January 11, 2011 10:52 AM >> To: [email protected] >> Subject: Re: Register customer librairies like we do for JRE lib >> >> Hmmm. >> >> I think I recall Guillaume saying that you could achieve this by just >> dropping them into a lib/ext directory? >> >> However, I prefer the idea of a 'Jar' deployer: if you drop a plain JAR >> into the deploy directory, then it should depoy using wrap (and making >> all dependencies marked for optional resolution to assist ease of use). >> >> Best, >> Ade. >> >> On 10/01/2011 21:46, Charles Moulliard wrote: >> >>> Hi, >>> >>> I would like to know if we have a property that we can setup to >>> register additional jar librairies (defined in a client folder >>> directory) like we do for JRE runtime libraries and expose them as >>> packages ? If this is not the case, could the hot "deploy" folder be >>> the alternative ? >>> >>> Regards, >>> >>> Charles Moulliard >>> >>> Sr. Principal Solution Architect - FuseSource >>> Apache Committer >>> >>> Blog : http://cmoulliard.blogspot.com >>> Twitter : http://twitter.com/cmoulliard >>> Linkedin : http://www.linkedin.com/in/charlesmoulliard >>> Skype: cmoulliard >>> >> > -- > Adrian Trenaman, Sr. Principal Solution Architect > FuseSource > Phone: +353-86-6051026 > Email: [email protected] > Web: http://trenaman.blogspot.com, http://fusesource.com > Twitter: adrian_trenaman > >
