OK, that's clear enough if a bit on the cumbersome side (remembering to keep adding dependencies).
On Sat, Jul 24, 2010 at 3:32 AM, Stephen Connolly <stephen.alan.conno...@gmail.com> wrote: > Sorry that should read: "put the execution in its own module and make that > module depend on all the other modules (which will force that module to the > end of the build plan)" > > Wouldn't want you having it depend on just half of the modules (every other > == every second) ;-) > > -Stephen > > On 24 July 2010 08:30, Stephen Connolly > <stephen.alan.conno...@gmail.com>wrote: > >> put the execution in its own module and make that module depend on every >> other module (which will force that module to the end of the build plan) >> >> >> On 23 July 2010 22:50, Benson Margulies <bimargul...@gmail.com> wrote: >> >>> I want to add a project that runs the maven-invoker-plugin to the end >>> of a large, multi-module build. How do I ensure that this runs at the >>> end and does not get shuffled by the reactor to some earlier point? Do >>> I have to add dependencies to the project? >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >>> For additional commands, e-mail: users-h...@maven.apache.org >>> >>> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
