Oh there's a lot to go before we can get here... I just had the idea of
where my end goal was and needed to write it down for when we get 3.5.0 out
the door and I've got the scope for 3.5.1 agreed and I have some time to
pick up my spec for 5.0.0 wiki page to bring it to a completed proposal
On Sa
This kind of overlaps with MNG-6118, which is also about the path to the
end-result.
I haven't thought about excluding some pieces of the lifecycle by default,
but we should focus more on the result.
Maven should react much better on the execute location within a
multimodule project and wha
So I am thinking the lifecycle should support the concept of *optional*
phases.
If no subsequent phase depends on the output of an optional phase, and the
optional phase was not explicitly called out on the invocation request,
then Maven could drop the phase.
By way of example, all the current te
