You may be right. Having said that, this XML parsing is done each time
that a dependency is declared by a configuration. I see this approach as
more self-contained than a solution based on the build system. Indeed,
this approach allows to declare the runtime dependencies of a
dependency, which is rather handy.
Also, I think that it is also a pain to declare the transitive
dependencies in a configuration. I would prefer to simply define the top
level dependencies, e.g. the ones defining the declared GBeans, and let
them define the other dependencies.
Thanks,
Gianny
On 20/10/2005 2:40 PM, Bruce Snyder wrote:
On 10/19/05, Gianny Damour <[EMAIL PROTECTED]> wrote:
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.
I'm not shooting down anything, but that sounds like a lot of extra
XML parsing. I'm curious to hear Dain chime in here to describe
exactly what he's doing with the Maven repo management code.
Bruce
--
perl -e 'print unpack("u30","D0G)[EMAIL
PROTECTED]&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
The Castor Project
http://www.castor.org/
Apache Geronimo
http://geronimo.apache.org/
