Right. I just thought that there was an exception to m-install-p (and
m-deploy-p) that they needed to be v4 as there has been changes to
build/consumer pom which they need to know about. That not being the case
is nicely done!
/Anders
On Thu, Jan 23, 2025 at 8:43 PM Tamás Cservenák wrote:
> htt
https://gist.github.com/cstamas/b0605a9fad09de4adcbd888baa4c
This above is just to get the idea: so Maven N will support Maven
Plugin N-1, or in other words, Maven 4 will fully support Maven 3
plugins (but not Maven2 plugins).
T
On Thu, Jan 23, 2025 at 8:15 PM Anders Hammar wrote:
>
> OK. I
OK. I incorrectly thought that I needed to use m-install-p v4 with Maven 4.
I just tested with m-install-p 3.1.1 and see that it works. Thanks for
clarifying!
/Anders
On Thu, Jan 23, 2025 at 11:35 AM Tamás Cservenák
wrote:
> Howdy,
>
> Yes, plugins are lagging, as we currently focus on core.
>
Howdy,
Yes, plugins are lagging, as we currently focus on core.
Given it works with Maven 3 plugins as well... you can still use Maven
4 w/ Maven 3 plugins.
T
On Thu, Jan 23, 2025 at 10:23 AM Anders Hammar wrote:
>
> It seems in fact that m-install-p 4.0.0-beta-1 is incompatible with Maven
> 4.
It seems in fact that m-install-p 4.0.0-beta-1 is incompatible with Maven
4.0.0 RCs. Using m-install-p 4.0.0-beta-2-SNAPSHOT from master seems to
work though. m-install-p 4.0.0-beta-1 has a dependency to Maven
4.0.0-beta-2 and there have been some API changes since.
So IMHO there is currently no e
