+1
Totally also agree with upping to Java 17.
Working mostly on Trino these days and we have been on 17 for quite a
while and are getting ready to go to 21 soon after it hits. In my
opinion Maven should do the same. There should be no reason not to
support and also default to the latest LTS.
Ultimately users who are good with using old JDK should also be good
with using an old build tool and an old IDE and so on..
And of course they also want to use old dependencies with many nice
security issues... so lets enable them to stop this by making the usage
of old stuff even more painful.
Manfred
On 2023-05-31 03:00, Tamás Cservenák wrote:
+1 for the move to Java 17 with Maven 4 (am actually for "move to latest
current Java LTS")
As anyone can see, all the major (OSS) projects did or are in the middle of
pushing for Java 17.
In September we have Java 21. The Java release cadence has changed, and it
did not change yesterday, but a long time ago, so users should live with it.
T
On Wed, May 31, 2023 at 10:30 AM Guillaume Nodet <gno...@apache.org> wrote:
I'd like to resume this discussion about switching master to require JDK
17.
These past days, I've been working on improving the usage of toolchains
(first inside maven, but now completely in the maven-toolchains-plugin)
with [1]. If we want to go further, we could simplify the selection by
modifying the POM somehow to add a specific section, but I suspect most
people will just use the release flag on the compiler to target bytecode.
The only downside I see, beyond the additional configuration (though the
goal is that users don't really have to generate/maintain the toolchains)
is that the selection of the toolchain is done during the build, so that
JDK profile based activation can not be used. Note that the use of
environment variables is also another way to work around, for example in
github [2].
I think with those improvements, requiring JDK 17 for master should be
doable. Any concerns of suggestions ?
Cheers,
Guillaume
[1] https://github.com/apache/maven-toolchains-plugin/pull/14
[2]
https://github.com/B3Partners/kadaster-gds2/blob/b0cd5c392bc1f48dec11c83c828254a868264467/.github/ubuntu-toolchains.xml
Le mar. 19 juil. 2022 à 18:25, Karl Heinz Marbaise <khmarba...@gmx.de> a
écrit :
Hi to all,
what do you think about using JDK17 as minimum requirement for running
the future Apache Maven 4.0.0 ?
Kind regards
Karl Heinz Marbaise
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
--
------------------------
Guillaume Nodet
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
