On Feb 12, 2007, at 5:29 PM, Jim Marino wrote:
On Feb 12, 2007, at 5:17 PM, Rick Rineholt wrote:
You list the dependencies here in the parent pom then in child
poms you don't list the version's and they use the parents. One
means of controlling the version you're using across multiple sub
projects in one place.
Jean-Sebastien Delfino wrote:> Why does
sca/pom.xml contain all the following dependencies?
With the modular build system we won't require these dependencies
this far up in the build tree anymore. As we group modules by how
they are distributed, we will be able to specify depedencies along
distribution lines. For example, all things related to Axis may
require a certain version of the Servlet API. This will give us
more flexibility and allow modules to require different versions of
particular libraries.
This may be a good time to continue refactoring the build tree as
as we discussed, in particular reorganizing the various modules
under java/sca/services as java/sca modules and pushing the
dependencies outlined by Sebastien down to that level.
Thoughts?
Jim
Yes. I have been pushing dependencies down into the modules where
possible (e.g. into kernel, runtime etc.) but I left all of them in
the parent pom as the extensions were still relying on them. IMO all
of these should be removed.
--
Jeremy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
