Dependencies are inherited in an aggregate fashion. So if you have common dependencies then you can state them in a parent project. In much the same way the Jelly tag builds are setup.
I did not wish to put all of the depends into a parent project as that would force each child project to have additional dependencies on its classpath which might not be a good thing, nor do I want each and every module to try to download SNAPSHOTS, especially if they do not even need that depend.
Sorry, don't understand that one. You want a common set of dependencies but don't want them in the classpath? What do you want to use those common dependencies for?
I think the problem is that you might want to put shared dependencies into a parent project file for a reactor project which has, for example, 20 sub-projects/components. But if perhaps only 10 of them actually use the dependencies, they will still have to be available for building the others individually. Of course, you can specify the dependencies individually in each component but then you have to maintain all the versions separately even though you want to use the same version throughout. Does the standard artifact version stuff you mentioned cover this scenario?
The dependency list is also useful high-level documentation on what is required for each component and how it works, but this information is lost if it is put in the parent file.
Luke.
-- Luke Taylor. Monkey Machine Ltd. PGP Key ID: 0x57E9523C http://www.monkeymachine.ltd.uk
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
