Plugin authors and executing parallel lifecycles

[Mohan KR <km...@gmail.com>]

With all the headaches with plugins forking a parallel lifecycle, really
looking for insights on the motivation

for it? Is it to maintain the integrity of the executing mojo task, that is
certain pre-conditions (phase) must be

met, before the actual execution.

 

The problem I'm facing is with a multi-module project during site
generation, I have a number of plugins

that are forking a parallel lifecycle and it is wreaking havoc, I wish I
could turn them off without hacking

the plugin.

 

Won't an option to introspect the current "phase" within the mojo give the
plugin authors some flexibility in

making the right call? 

 

 

Thanks,

mohan kr