Please always keep replies on the list for future queries. On 30 March 2011 12:56, <[email protected]> wrote: >>> At the root project create a profile for running these tasks, e.g. >>> >>> <profile> >>> <id>my-superugly-hack</id> >>> ... >>> </profile> > >>> into that profile you put a <build> section with a <defaultGoal> >>> containing all the stuff you want to do separated by spaces > > Yes - works as expected, thank you very much! > > Care to elaborate why you consider this to be a superugly-hack? > > - because I have to call so many goals to circumvent maven limitations (at > least I didn't find another way yet), or
Nope > - because using a profile this way is not recommended or More that specifying anything other than a single lifecycle phase is not supposed to be supported IIRC... so you are relying on a bug => hack > - both ? > > If anyone tells me another way how to call some goals after all childs > have been built, I'm happy to use this instead! 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.... Note that you may run into issues if you require to fetch something out of the reactor for your subsequent invokations... but at least you can have invoker invoke all the goals in one go... and that is a supported way to invoke multiple goals > > Cheers > Stefan > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
