On 4/12/10 4:02 AM, Karl Heinz Marbaise wrote: > ... > Maybe i misunderstand the usage of a module ...or do i have to give simply > the modules m4.1...m4.5 as dependency instead of using m4? > > The m4 module is a aggregation of multiple modules (m4.1...m4.5) which are > needed as dependency so it would be nice just to give m4 as dependency.... > This is the source of your misunderstanding. m4 is an aggregation for build purposes ONLY. It is not an aggregation of the artifacts and sub-modules are not considered when calculating the dependency tree.
> Or does exist an other solution to handle such a problem? If your "problem" is that you don't want to explicitly declare five dependencies in m3.2, I don't really consider that a problem. You're saving like 90 seconds in copying-and-pasting. But if you really wanted, you could create an intermediate project which "aggregates" dependencies the way you want, just via the <dependencies> element, i.e. m3.2 depends upon m4.a m4.a depends upon m4.1, m4.2, m4.3, etc. I'm pretty sure m4.a needs to be a JAR project, but I could be wrong about this. Justin > > Kind regards > Karl Heinz Marbaise --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
