On Jan 5, 2006, at 1:55 PM, Sean Schofield wrote:
The other cool thing with a 'parent pom' is that you'd only specify
the dependency version once in the top level pom so that we would not
have to change it over and over again in the subprojects/modules.
I can't think of a single dependency that would apply to *all*
projects. If it doesn't apply to all modules then you don't want it
in the "root" POM do you? Otherwise it shows up in the dependency
reports even though the dependency is not there ...
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.
We wouldn't put commons in the top level POM either would we? That
isn't even created until later on down the line. Plus different
modules would depend on different versions (since we are releasing
independently now ..)
Well I'd set the dependency during the development cycle to be
consistent. Then at release time for a module you could fix it to the
version you are about to release, publish the module then fix it back
to the snapshot version.
I'm not sure the process is fully baked in my mind though. I'll have
to put another thread out for discussion on that.
-bd-
-bd-
Sean
