maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andreas Gudian <>
Subject Re: Building selected projects with nested aggregators
Date Fri, 12 Apr 2013 05:59:48 GMT

just use the directory notation. The following will build the module
in module-dir/sub-module-dir
and all the modules in the reactor that depend on it:

mvn test -pl module-dir/sub-module-dir -amd


Am Freitag, 12. April 2013 schrieb spoots :

> 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:
> <>
> Now pretend that project "streaming-client" has a dependency on project
> "client-web". If I do a build of "big-system", Maven will put "client-web"
> ahead of "streaming-client" in the reactor order which is dandy - it seems
> to walk the whole project tree and resolve the dependencies just fine.
> But how can I specify, from the top level, to build "client-web" and all
> it's dependents if I change just that one project? Using the "-pl" option
> from within "big-system" seems to only recognise project names that are
> directly included in that reactor (e.g. "server-side" and "client-side").
> Is
> there some kind of qualifier that lets me specify a project which is nested
> within another aggregator project?
> Thanks,
> Keith
> --
> View this message in context:
> Sent from the Maven - Users mailing list archive at
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: <javascript:;>
> For additional commands, e-mail:<javascript:;>

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message