On Dec 28, 2013 7:46 PM, "Karl Heinz Marbaise" <khmarba...@gmx.de> wrote:
>
> Hi to all
>
> 2. This plugin currently forks the life-cycle compile (generate):
>
>    The question is: Why is this necessary (may be i misunderstand
>    a thing with those forking of the life-cycle)?
>    Wouldn't it be better having different goals (one which forks
>    an other which doesn't) to give the user the chance to decide
>    which to use?

Hello Karl Heinz,

guessing: for the standalone execution phase compile gave the author the
compile class path automatically?
I dislike it when goals fork needlessly as this will lengthen build time
considerably. IMO it would be great if you could at least add a '-no-fork'
variant of the goal :).

Reply via email to