On 30 March 2011 13:27, <stefan.han...@tolina.com> wrote: >>> Please always keep replies on the list for future queries. > Sorry, answered to the wrong mail, will keep an eye on it in the future. > >>> Maven invoker plugin could do what you want... you would bind it in a >>> profile to e.g. the validate phase of the lifecycle. then you can use >>> defaultGoal as validate and have invoker invoke all that you need.... > > I tried that first! (see the config from my first post) > But in a multimodule build I get an unwanted recursion.
1. needs to be bound in a non-default profile 2. needs to have <inherited>false</inherited> to stop the child projects running invoker 3. need to set invoker.nonRecursive or invoker.nonRecursive.N where N is the invokation you want only on the root pom. > > Think of invoker plugin, bound to validate, just calling 'site'. > Now running: > > mvn -PinvokerPluginCallingSite > > starts a reactor build with the phase validate in the following order: > [INFO] ----------------------------------------- > [INFO] Reactor Build Order: > [INFO] > [INFO] Master > [INFO] MasterSub1 > [INFO] MasterSub2 > [INFO] > > and now invoker-plugin calls site for > Master => (still a full multimodule build, which runs site for Master, > MasterSub1, MasterSub2) > MasterSub1 => (unwanted extra site) > MasterSub2 => (unwanted extra site) > > That's why I didn't succeed with the invoker plugin. > > Cheers > Stefan > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
