geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joe Bohn <>
Subject Re: Shared Libs
Date Wed, 05 Apr 2006 19:55:05 GMT
I think the shared libraries may solve this issue for a lot of people.

Do you have some more thoughts on how this capability may be made 
available to users?  Looking at what was checked in already it seems 
that the user would have to create an array of the libDirs in code via 
some home-grown mechanism and then invoke your class to update the 
classpath.   Do you already have plans for an easier way to expose this 
to the users (perhaps via some server configuration or some new elements 
on the deployment plans to add new shared libraries)?


Dain Sundstrom wrote:
> One new feature I'm working on for 1.1 is support for tomcat style  
> shared libs.  This creates a shared class loader visible to all j2ee  
> applications which contains shared/lib/*.jar and shared/classes/ to  the 
> class loader.
> Will this address your issues?
> -dain
> On Apr 4, 2006, at 7:35 PM, Joe Bohn wrote:
>> I have a situation where I need to make several web modules  dependent 
>> upon a large number of jars.  I'd like to add the jars to  the 
>> Geronimo repo and add the dependencies into the plans for the  web 
>> modules. However, most of the jars don't follow the maven  naming 
>> convention because the names don't include a version (and  I'd rather 
>> not rename all the jars).
>> I know that there are changes being included in 1.1 to make the  
>> version in a reference optional.  However, I doubt that it is  
>> possible to reference a jar in the repo that doesn't contain any  
>> version.  Just thought I should ask in case it really is possible.   I 
>> could see where this might be something users would like when  they 
>> have picked up jars from various places which may or may not  contain 
>> a version in the jar name.
>> If it *is* possible to have a non-versioned jar in the repo ... how  
>> do we differentiate in geronimo 1.1 between a dependency on a non- 
>> versioned jar versus a dependency on the latest version of a jar  (in 
>> case both are present).
>> Thanks for the help,
>> Joe
>> -- 
>> Joe Bohn
>> joe.bohn at
>> "He is no fool who gives what he cannot keep, to gain what he  cannot 
>> lose."   -- Jim Elliot

Joe Bohn
joe.bohn at

"He is no fool who gives what he cannot keep, to gain what he cannot 
lose."   -- Jim Elliot

View raw message