Re: [DISCUSS] Java version for Maven

On Mon, Feb 26, 2024 at 7:24 PM Benjamin Marwell wrote: > > > 1. The Java version required by the project being built. That is, the > byte code and API level of the project. > > 2. The Java version used to compile the project. > > 3. The Java version used to run Maven. > > 4. The Java version

Re: [DISCUSS] Java version for Maven

On Tue, Feb 27, 2024 at 1:33 PM Elliotte Rusty Harold wrote: > but that only goes so far. There's a fundamental problem that > toolchains are incompatible with a hermetic, one click build. > > Why so? Could you elaborate? T > -- > Elliotte Rusty Harold > elh...@ibiblio.org > >

Re: [DISCUSS] Java version for Maven

On 2/26/24 11:42 AM, Basil Crow wrote: We had a similar conversation in the Jenkins community, and I wrote up our conclusions here: We also had a similar conversation in the NetBeans community, with the final vote to drop JDK 8 (vote result: 20 to 1.5). See here: [VOTE][RESULT] Minimum JDK

Re: [DISCUSS] Java version for Maven

On 2/25/2024, 2:49 PM Elliotte Rusty Harold wrote: >> For #2, reproducible builds mean we have to be able to support what >> customers are using and that can be anything from Java 8 - 21. It is >> not sufficient to say Java 21 can compile to Java 8 since that does >> not produce the same byte

Re: [DISCUSS] Java version for Maven

On Tue, 27 Feb 2024 at 17:01, Benjamin Marwell wrote: > > > Compiling for Java 8 with > > Java 17 -release 8 is not the same as compiling with javac from JDK 8. > > They do not produce the same byte code. There is a need to compile > > *with* JDK 8, not just compile *for* JDK 8. > > And when

Re: [DISCUSS] Java version for Maven

whose vote would count and what be the majority:) for example should my vote count? or not? or just some committers? but why just committers(or not)(as some of them might have less contributions even than non-committers)? or just pmc? or everyone share 1 vote(wow I don't think it shall work this

Re: [DISCUSS] Java version for Maven

On Tue, Feb 27, 2024 at 6:13 PM Romain Manni-Bucau wrote: > Not sure we'll converge guys but shouldnt we make a vote? Seems we all > understand the impacts technically so maybe time to decide else we'll still > be there in a year. > This is exactly what I try in the Eclipse community - vote,

Re: [DISCUSS] Java version for Maven

> Compiling for Java 8 with > Java 17 -release 8 is not the same as compiling with javac from JDK 8. > They do not produce the same byte code. There is a need to compile > *with* JDK 8, not just compile *for* JDK 8. And when would that be needed? On Tue, 27 Feb 2024, 13:33 Elliotte Rusty

Re: [DISCUSS] Java version for Maven

Plain standard asf votes - or under the vote manager rules as allowed by asf if it is agreed but means another discussion. I dont care much the details but keeping energy for this thread starts to be more negative on the community than anything positive IMHO so hope we close it with a decision

Re: [DISCUSS] Java version for Maven

On Tue, Feb 27, 2024 at 8:16 PM Xeno Amess wrote: > whose vote would count and what be the majority:) > for example should my vote count? or not? > or just some committers? but why just committers(or not)(as some of them > might have less contributions even than non-committers)? > or just pmc? >

[VOTE] Require Java 17 for Maven 4

Hi Maven Devs/Users/Committers and PMC members! After several discussions on the mailing lists, I would like to start a vote in favour of setting the minimal Java bytecode target of Maven-Core 4 to 17 and hence require Java 17 for Maven 4. This is a procedural majority vote [1*]: You can also

Re: [VOTE] Require Java 17 for Maven 4

+1 On 28/02/2024 08.30, Benjamin Marwell wrote: Hi Maven Devs/Users/Committers and PMC members! After several discussions on the mailing lists, I would like to start a vote in favour of setting the minimal Java bytecode target of Maven-Core 4 to 17 and hence require Java 17 for Maven 4. This

Re: [VOTE] Require Java 17 for Maven 4

+1 (set JDK17 min version for Maven 4.x)

Re: [DISCUSS] Java version for Maven

> people will be able to work on solutions after anyway. Agreed as they can maintain a fork anyway if they really need. From: Romain Manni-Bucau Sent: Wednesday, February 28, 2024 3:50:31 AM To: Maven Developers List Subject: Re: [DISCUSS] Java version for Maven

Re: [DISCUSS] Java version for Maven

Hi Hervé Im not sure why there is this belief toolchain improvement is needed, this is NOT needed and CI already bypass it so for me this is not an enabler, more a blocker IRL. Let's improve plugins if they dont enable executable/env config but toolchain is just a part of the execution of so

Re: [DISCUSS] Java version for Maven

Le lundi 26 février 2024, 13:42:19 CET Ceki Gulcu a écrit : > Hello Bernd, > > I was unaware of the capabilities of the release flag. Thank you for > explaining. a proof that even capabilities like --release flag from JDK 9 (JEP 247 https:// openjdk.org/jeps/247) need to be promoted because it's

Re: [VOTE] Require Java 17 for Maven 4

+1 (non binding) On Wed, Feb 28, 2024 at 8:31 AM Benjamin Marwell wrote: > Hi Maven Devs/Users/Committers and PMC members! > > After several discussions on the mailing lists, I would like to > start a vote in favour of setting the minimal Java bytecode target > of Maven-Core 4 to 17 and hence

Re: [VOTE] Require Java 17 for Maven 4

+1 Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github | LinkedIn | Book

Re: [VOTE] Require Java 17 for Maven 4

+1 /Anders On Wed, Feb 28, 2024 at 8:30 AM Benjamin Marwell wrote: > > Hi Maven Devs/Users/Committers and PMC members! > > After several discussions on the mailing lists, I would like to > start a vote in favour of setting the minimal Java bytecode target > of Maven-Core 4 to 17 and hence

Re: [DISCUSS] Java version for Maven

Le mardi 27 février 2024, 18:33:43 CET sebb a écrit : > On Tue, 27 Feb 2024 at 17:01, Benjamin Marwell wrote: > > > Compiling for Java 8 with > > > Java 17 -release 8 is not the same as compiling with javac from JDK 8. > > > They do not produce the same byte code. +1 that's a fact > > > There is

Re: [DISCUSS] Java version for Maven

Le mardi 27 février 2024, 13:32:36 CET Elliotte Rusty Harold a écrit : > Toolchains support using JDK 8 to compile even though JDK 17 is > executing Maven, which does handle this. Unfortunately toolchains are > poorly designed, badly documented, and not widely understood within > the community.

Re: [DISCUSS] Java version for Maven

At this point, we have discussed many aspects. Please feel to vote: User List: https://lists.apache.org/thread/ty321ns72qc6l26bjy58d9430ofg2w5t Dev List: https://lists.apache.org/thread/vngchrr3owd92v9y09lyfjjhwkl5hvtn - To

Re: [VOTE] Require Java 17 for Maven 4

+1 Sylwester śr., 28 lut 2024 o 08:40 Romain Manni-Bucau napisał(a): > +1 > > Romain Manni-Bucau > @rmannibucau | Blog > | Old Blog > | Github < > https://github.com/rmannibucau> | >

Re: [VOTE] Require Java 17 for Maven 4

+1 (non binding) Romain Manni-Bucau 于2024年2月28日周三 15:40写道： > > +1 > > Romain Manni-Bucau > @rmannibucau | Blog > | Old Blog > | Github | > LinkedIn

Re: [VOTE] Require Java 17 for Maven 4

+1 as a user +1 as Project Lead of Tycho that already requires java 17 for a few years now and soon will be Java 21 +1 as Project Lead of m2e that already is on Java 17 and needs to maintain some code in Java 8 to retain support for Maven Am 28.02.24 um 08:30 schrieb Benjamin Marwell: Hi

Re: [DISCUSS] Java version for Maven

Not sure we'll converge guys but shouldnt we make a vote? Seems we all understand the impacts technically so maybe time to decide else we'll still be there in a year. Le mar. 27 févr. 2024 à 16:41, John Neffenger a écrit : > On 2/26/24 11:42 AM, Basil Crow wrote: > > We had a similar