Out of my head, reusing the cli/clibuilder was easier and avoids all the
fork config we want to avoid for such command but guess both work.
Le sam. 11 janv. 2020 à 14:11, Enrico Olivelli a
écrit :
> Romain
>
> Il giorno dom 5 gen 2020 alle ore 18:14 Romain Manni-Bucau <
> rmannibu...@gmail.com>
Romain
Il giorno dom 5 gen 2020 alle ore 18:14 Romain Manni-Bucau <
rmannibu...@gmail.com> ha scritto:
> Hi Enrico
>
> Technically concatenating all goals for all modules will do it but will be
> quite long - guess it is why we do it in 2 times.
>
> That said i always wondered why maven can read
If you want to execute a plugin goal apart from a lifecycle, then I think it
should be for only one module.
So I'd expect the call more to be like -pl module -am
That said, if you know you want to execute this goal for 1 specific module, I
would like to be able to start from that pom and run "mvn
Hi Enrico
Technically concatenating all goals for all modules will do it but will be
quite long - guess it is why we do it in 2 times.
That said i always wondered why maven can read commands from a file/stdin
as any unix like soft so it would be something like:
mvn --commands-file ci.cmdlist
Us
Hello,
Sometimes it happens that you have to launch twice Maven to:
- build a whole reactor project (warmup)
- run some specific mojo only a selection of modules
mvn clean install -DskipTests -Dmaven.repo.local=tmprepo
mvn do:something -pl module1,module1-Dmaven.repo.local=tmprepo
I think that i
