Hello Tamas
Thanks for the explanation. Then I will pause the Maven compiler plugin
work for now and resume after the new master branches are ready (I need
to focus on 2 meetings in June anyway). Just for avoiding confusion,
would it be possible to delete the current "mvn4" branches?
Side note: if the "master" branch is going to be very different than the
current branch, would it be an opportunity to rename "master" as "main"?
It could be done by creating a new Maven 4 branch named "main", make it
the default when ready, then rename current "master" as "maven-3.x".
Martin
Le 2024-05-20 à 11 h 36, Tamás Cservenák a écrit :
Howdy,
maven-plugin-tools: We agreed with Guillaume to split it: instead of mvn4,
master will be "maven 4" and we will introduce a maven-3.x branch for
Maven3 support. Currently the master was meant to support both (maven3 and
maven4 plugins), but it proved problematic, hence the split. A plugin
cannot be both anyway, it is this or that hence the user can choose which
version, 3.x or 4.x wants to use.
plugin-testing: AFAIK, same stands here, due huge difference how those
operate (maven-core vs new maven API).
This is all yet to be done.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
