Re: [DISCUSS] New goal for install/deploy plugin?

Then I guess the new deploy logic is wrong since it does not enable to use the mojo as a mojo (outside a predefined lifecycle which is against mojo design) so should be relaxed (reverted?). Romain Manni-Bucau @rmannibucau | Blog

Re: [DISCUSS] New goal for install/deploy plugin?

I dislike the idea to "toggle logic". This way, we would have 3 mojos with 3 different logic. Is simpler to understand, that invoke same mojo to do this or that, based on toggle. T On Sat, Feb 25, 2023, 13:18 Romain Manni-Bucau wrote: > Hi, > > Maybe I missed some details but n unsafe toggle (p

Re: [DISCUSS] New goal for install/deploy plugin?

Hi, Maybe I missed some details but n unsafe toggle (parameter) to deploy sounds like a good compromise to me. Too much overlapping goals sounds weird and hard to understand. Le sam. 25 févr. 2023 à 12:39, Tamás Cservenák a écrit : > Howdy, > > Here is this thread: > https://lists.apache.org/th

[DISCUSS] New goal for install/deploy plugin?

Howdy, Here is this thread: https://lists.apache.org/thread/lbbd5n92xjksyf53mlf12togxrvdbvhl In short, user is _partially_ building a module, and invokes deploy:deploy, that now fails, as since 3.x version of install/deploy, there is a "safety check" in these mojos, to not deploy partially (here