Le dimanche 21 janvier 2024, 22:03:59 CET Guillaume Nodet a écrit :
> At build time, I think it's fine to bump to whatever is needed to make
> our life manageable. If 17 is required, so be it.
+1
my biggest concern with Maven 4 is not JDK runtime requirement, but plugins
future when a plugin
Definitely the improvement is targeting Maven 4 API, hence only plugins
using Maven 4 API would benefit from it.
Backporting this to Maven 3 is nearly impossible.
Basically what we have in Maven 3 (and related plugins, that fiddle with
classpath/modulepath) is what we stay with in Maven 3
Le 2024-01-22 à 09 h 52, Hervé Boutemy a écrit :
are there known features in Maven 4 API not available in Maven 3 that
would bring stronger interest in writing a goal for Maven 4?
If accepted, the way to determine where to put dependencies (class-path,
module-path, etc.) would require Maven
Le lun. 22 janv. 2024 à 13:34, Benjamin Marwell a
écrit :
> To add some more information, I have seen some extreme reduction in
> build times after switching from Java 11 to 17 or even 21 (just for
> build, not the runtime).
> We can still verify it runs on 11/17 by using the integration tests,
To add some more information, I have seen some extreme reduction in
build times after switching from Java 11 to 17 or even 21 (just for
build, not the runtime).
We can still verify it runs on 11/17 by using the integration tests,
but having the (possibly parallel) unit- and integration tests
I agree with observations ... in the Trino project we switched to
require Java 17 ages ago and now switched to 21 for the project itself.
The language improvements to 17 and then to 21 allow for a lot of code
improvements on the source level.
As a build tool that supports building other
Le lun. 22 janv. 2024 à 09:52, Hervé Boutemy a écrit :
>
> Le dimanche 21 janvier 2024, 22:03:59 CET Guillaume Nodet a écrit :
> > At build time, I think it's fine to bump to whatever is needed to make
> > our life manageable. If 17 is required, so be it.
> +1
>
> my biggest concern with Maven 4
I'm close to Ben and Manfred,
I think Maven can get a lot of value (for maintaining as for runtime) by
switching to Maven 21 a base for itself.
Matthias
Am 22.01.2024 um 13:33 schrieb Benjamin Marwell:
To add some more information, I have seen some extreme reduction in
build times after
