On Oct 19, 2005, at 9:57 PM, Gianny Damour wrote:
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.
Could you explain what you mean by this?
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.
That is certainly a goal I like :-).
I like the idea of constructing the geronimo-service.xml's from the
project.xml. That would eliminate one source of duplication. And, we
could open up the configurations and possibly jars included explicitly
in an assembly and extract the dependencies and install them into the
geronimo repo providing they are available. However, unless maven is
also keeping track of the transitive dependencies somehow, such as
through poms, I don't see how maven will be able to guarantee that all
the dependencies needed for an assembly are actually present in the
local maven repo, so we can copy them. Any ideas?
thanks,
david jencks
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/
