Le 2024-05-21 à 11 h 18, Guillaume Nodet a écrit :
https://github.com/Geomatys/maven/commit/5165ca60a1b44cd2a376cd1bfe48f558a2cbd54f
looks interesting, as the interface was introduced in 4.x branch, so no
need to keep it as it's not used anymore. Feel free to create a proper PR.
Thanks, done.
And
https://github.com/Geomatys/maven/commit/5165ca60a1b44cd2a376cd1bfe48f558a2cbd54f
looks interesting, as the interface was introduced in 4.x branch, so no
need to keep it as it's not used anymore. Feel free to create a proper PR.
Le mar. 21 mai 2024 à 11:15, Guillaume Nodet a écrit :
>
>
> L
Le lun. 20 mai 2024 à 11:37, 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
> mav
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 no
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
c
Hello all
I'm trying to run the tests on the reworked compiler plugin for Maven 4,
but execution is having an issue with Maven dependency injection. Before
to give more details, I would like to check if I'm up to date.
Three months ago, I was told to use the following branches:
* Maven core
