karaf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Adrian Trenaman <trena...@progress.com>
Subject Re: Register customer librairies like we do for JRE lib
Date Tue, 11 Jan 2011 09:51:47 GMT

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).


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
Phone: +353-86-6051026
Email: trenaman@fusesource.com
Web: http://trenaman.blogspot.com, http://fusesource.com
Twitter: adrian_trenaman

View raw message