Re: Building selected projects with nested aggregators

Thanks for the reply, again :) I don't think "-amd" covers my need though. Because there's no parent/child relationship between the modules/sub-modules there's no dependency between them. It feels to me like there's an option missing for the reactor here... A simpler example for clarity: <

Re: Building selected projects with nested aggregators

Oops, just realised this scenario doesn't quite reflect my situation. Please also imagine in the attached image that there is no parent/child relationship between "webapps" and it's sub-modules, i.e. it's purely an aggregator POM -- View this message in context: http://maven.40175.n5.nabble.c

Re: Building selected projects with nested aggregators

Sorry to bump my own thread, but I've got a another use-case and I'm hoping there's a similarly blindingly obvious solution :) What if I want to build all the sub-modules of, say, "web-apps" and their dependencies across the whole tree? I know I can go in to the "web-apps" aggregator and do a "mvn

Re: Building selected projects with nested aggregators

Bingo! I can't believe I never tried that, but it works perfectly. Thank you :) -- View this message in context: http://maven.40175.n5.nabble.com/Building-selected-projects-with-nested-aggregators-tp5753572p5753574.html Sent from the Maven - Users mailing list archive at Nabble.com. -

Building selected projects with nested aggregators

Hi, I've got a project structure where I have an aggregator project and all of it's modules are also aggregator projects (i.e. projects that exist just to specify sub-modules). Picture something like what's shown in the "POM best practices" section of the Maven reference: