Was happy too soon.
If I move the invoker plugin profile to my company-parent pom, then all
steps to remove the recursion problem make it not work anymore for my
multimodule build :(
-
To unsubscribe, e-mail: users-unsubscr..
>> 1. needs to be bound in a non-default profile
>> 2. needs to have false 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.
Now invoker plugin is doing what I want now!
Thanks
On 30 March 2011 13:27, 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 lifecy
>> 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
Please always keep replies on the list for future queries.
On 30 March 2011 12:56, wrote:
>>> At the root project create a profile for running these tasks, e.g.
>>>
>>>
>>> my-superugly-hack
>>> ...
>>>
>
>>> into that profile you put a section with a
>>> containing all the stuff you wan
Also it is important to note that this trick only works if the profile
id contains the string "-superugly-hack"
On 30 March 2011 12:34, Stephen Connolly
wrote:
> At the root project create a profile for running these tasks, e.g.
>
>
> my-superugly-hack
> ...
>
>
> into that profile you put a
At the root project create a profile for running these tasks, e.g.
my-superugly-hack
...
into that profile you put a section with a
containing all the stuff you want to do separated by spaces
ideally you would also configure all the executions and the
default-cli executions of the mojos
>> Bind the goals you want to run to chosen phases.
This unfortuntaly is not possible in a multimodule build, let's take the
dashboard plugin as an example:
The dashboard:dashboard needs to run AFTER the full site has been created
in a multimodule build (because it needs access to all checksty
Bind the goals you want to run to chosen phases.
This is done in through build/plugins/plugin/executions/execution in your
pom
--
View this message in context:
http://maven.40175.n5.nabble.com/changing-a-long-mvn-command-with-many-goals-to-a-simple-command-tp4271214p4271230.html
Sent from the Ma
