Hi Wendy,
On Jan 5, 2006, at 2:18 PM, Wendy Smoak wrote:
On 1/5/06, Bill Dudney <[EMAIL PROTECTED]> wrote:
Well if more than one of the modules depends on it (not all) then I'd
put it in the root. That way your are consistently specifying the
version you depend on. As far as the dependency report goes each
module will get a more specific one, the top level will define all
the dependences for everything. In some respects it could be
considered better to have the top level specify each and every
dependency even if its only used in one module.
I don't agree with this at all. For one thing, any webapps you try to
build will inherit all of the dependencies and they will all land in
WEB-INF/lib. You'll then have a mess of exclusions trying to keep
things out. And the list of dependencies will be useless to someone
trying to figure out what any one module really depends upon. I
haven't tried it, but I'm also concerned that the poms created during
the release process will list too many dependencies.
Do we really end up with everything from the top level in the lib
dir? What I'm thinking is something like this being in a 'user' project.
<dependency>
<groupid>org.apache.myfaces</groupId>
<artifactId>tomahawk</artifactId>
</depdency>
This will cause the transitive dependency thing to pull in everything
that tomahawk depends on but won't touch the top level pom as I
understand it anyway. Am I wrong about this?
For Struts I'm resisting putting *any* dependencies in the parent pom,
even if it means repeating a couple of them (servlet-api and junit).
In practice, the transitive dependency mechanism will work better than
inheritance for making sure each module has the dependencies it needs
to compile.
I hate to repeat the info though...
--
Wendy
