Hi Chris, Yes, you can list a greater depth in two ways: - add the extra path - add extra parent poms at different levels, if that is appropriate
For the first, in top: <modules> <module>g/h</module> ... </modules> For the second, it would be this in top: <modules> <module>g</module> </modules> and in g: <modules> <module>h</module> </modules> These are effectively the same, but if you have that inheritance structure the second gives a more natural grouping (eg, you can cd into "g" and build all its subprojects only). If you do the first solution, the children poms sohuld have the following hint in the parent element: <parent> ... <artifactId>top</artifactId> <relativePath>../../pom.xml</relativePath> </parent> The repository is still used if ../../pom.xml is not found or the versions don't match, but the hint makes it easier to use local modifcations without installing the parent. - Brett On 1/5/06, Chris Berry <[EMAIL PROTECTED]> wrote: > Greetings, > Is it possible to specify multiple <modules> in a POM that are "deeper" than > 1 level. > In other words, say I have the following structure: > /top/pom.xml <== the multi-module POM > /top/a/b/c/d/pom.xml <== build 1 > /top/a/e/f/pom.xml <== build 2 > /top/g/h/pom.xml <== build 3 > > How can I type "maven install" in /top and have build 1,2,3 built > I have searched the List archives and the site docs, and cannot find any > pertinent info. My apologies if I missed it... > Thanks, > -- Chris > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
