geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gianny Damour <gianny.dam...@optusnet.com.au>
Subject Re: transitive dependencies
Date Thu, 20 Oct 2005 04:23:36 GMT
Another approach would be: for each plain dependency, we could generate 
a META-INF/geronimo-service.xml file based on the POM dependencies as 
part of a standard build. Transitive dependencies would be achieved by 
walking down the dependencies defined by the geronimo-service.xml file.

Thanks,
Gianny

On 20/10/2005 1:56 PM, David Jencks wrote:

> I've been working on building geronimo using the packaging and 
> assembly plugins.  This works fine except for the unmanageable 
> dependencies.   The project for the assemby plugin to work on 
> currently needs to include in the project.xml every jar to go into the 
> assembly's repository.  Tracking these is impossible.
>
> We need some way for a configuration or even a plain dependency to 
> instruct the assembly plugin to copy the artifacts dependencies into 
> the repository.
>
> One possibility is to use maven poms.  IIUC Dain is working on 
> integrating or imitating the latest maven repository management code.  
> Will this give us transitive dependencies?  Will the maven model work 
> for us?  How close is this?  If we had it, it would be pretty easy to 
> construct separate jetty and tomcat assemblies, a both assembly, an 
> assembly w/o ejbs, etc etc.  Without transitive dependencies, it will 
> be a nightmare to try to keep the repository contents adequate and 
> restricted to what is actually needed to run the server.
>
> thanks
> david jencks
>
>



Mime
View raw message