On Sun, 2003-08-17 at 00:16, Jason van Zyl wrote: > On Sat, 2003-08-16 at 16:35, Luke Taylor wrote: > > > > 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. > > Ok, that I don't quite understand. There is just a fear of polluting the > classpath?
Yeah, that would be my concern. For example, you might have certain sub-projects that shouldn't be doing anything with XML, but if you inherit all your dependencies from the parent project you loose the ability to verify these architectural constraints at compile time. Probably more important, if your project contains sub-projects common, framework, shared, front-end, back-end and ui, you might want to make sure that ui only depends on front-end, shared, framework and common, but that it's depending on the same versions of shared, framework and common that the back-end project is depending on. -Mark. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
