Re: [VOTE] Require Java 21 for Maven 4 (Rephrased Vote)

+1 (non-binding) - JEP 400: UTF-8 by Default (JDK18) - JEP 418: Internet-Address Resolution SPI (JDK18) - JEP 444: Virtual Threads (JDK21) regards Grzegorz Grzybek śr., 30 kwi 2025 o 21:50 Elliotte Rusty Harold napisał(a): > -1 > > On Wed, Apr 30, 2025 at 1:12 PM Matthias Bünger > wrote: >

Re: [HEADS UP] Maven 3.9.10 release

On 5/1/25 06:21, Guillaume Nodet wrote: > The only way is to add the --enable-native-access=ALL-UNNAMED option in the > shell scripts afaik. We've already added it in master. > Note that this option is not available in older JDK which are still > supported by Maven 3.9. -XX:+IgnoreUnrecognizedVMO

Re: [HEADS UP] Maven 3.9.10 release

For grins, I updated guava to latest in 3.9.9 distribution. That issue went away then guice popped up. Guice can be updated to 6.0.0. However, that won't solve its warning and 7.0.0 is not usable with Maven 3.9.9 since its jakarta only. So not sure if that one is fixed at jakarta or not but

Re: [HEADS UP] Maven 3.9.10 release

The user can configure MAVEN_OPTS yes. Or .mvn/jvm.config. The real problem is that adding the option will fail if running on an older JDK which did not have that option. What we have in master is a snippet that detects if we're running on JDK 17. In the case of master, it's used to make sure Ma

Re: [HEADS UP] Maven 3.9.10 release

Could MAVEN_ARGS or MAVEN_OPTS be used for this? Gary On Thu, May 1, 2025 at 12:22 AM Guillaume Nodet wrote: > > The only way is to add the --enable-native-access=ALL-UNNAMED option in the > shell scripts afaik. We've already added it in master. > Note that this option is not available in older

Re: [HEADS UP] Maven 3.9.10 release

All good, I noticed the version of Guava used reports the same. I build myself a local 3.9.10 build and do some tests as well. Mark -- "Great artists are extremely selfish and arrogant things" — Steven Wilson, Porcupine Tree On 1 May 2025 at 4:21:57 PM, Guillaume Nodet wrote: > The only w

Re: [HEADS UP] Maven 3.9.10 release

The only way is to add the --enable-native-access=ALL-UNNAMED option in the shell scripts afaik. We've already added it in master. Note that this option is not available in older JDK which are still supported by Maven 3.9. Guillaume Nodet Le jeu. 1 mai 2025 à 05:19, Ma

Re: [HEADS UP] Maven 3.9.10 release

Tamás, Guillaume - I note when running 3.9.9 under Java 24, I see: WARNING: A restricted method in java.lang.System has been called WARNING: java.lang.System::load has been called by org.fusesource.jansi.internal.JansiLoader in an unnamed module (file:/Users/amrk/.sdkman/candidates/maven/current/

Re: [DISCUSS] Publishing to Central + Maveniverse Njord

For snapshots, its vanilla. I'm pretty sure that support was only recently added. It's not using their plugin in that case. I do find that confusing to users and their docs were slightly unclear. Sent from my Verizon, Samsung Galaxy smartphone Get Outlook for Android _

Re: [VOTE] Require Java 21 for Maven 4 (Rephrased Vote)

-1 On Wed, Apr 30, 2025 at 1:12 PM Matthias Bünger wrote: > > Hi everyone, > over the last years we had several discussions about lifting the > required Java version to run Maven from 8 to something higher. You can > find them in the mail archive. > In February 2024 we decided to lift it to 17 (s

Re: [VOTE] Require Java 21 for Maven 4 (Rephrased Vote)

+1 (not binding) best regards, michael On 4/30/25 15:12, Matthias Bünger wrote: > Hi everyone, > over the last years we had several discussions about lifting the required > Java version to run Maven from 8 to something higher. You can find them in > the mail archive. > In February 2024 we deci

Re: [DISCUSS] Publishing to Central + Maveniverse Njord

Jeremy, Just to be clear, you are not in the "vanilla" space, as you are using a vendor plugin/extension, right? On Wed, Apr 30, 2025, 18:26 Jeremy Landis wrote: > FYI regarding deploy plugin I wanted to point out from personal experience > on the migration. > > maven deploy plugin still is use

Re: [VOTE] Require Java 21 for Maven 4 (Rephrased Vote)

+1 Arnaud Héritier GitHub/ASF/... : aheritier On Wed, Apr 30, 2025 at 15:12 Matthias Bünger wrote: > Hi everyone, > over the last years we had several discussions about lifting the > required Java version to run Maven from 8 to something higher. You can > find them in the mail archive. > In Fe

Fwd: [VOTE] Require Java 21 for Maven 4 (Rephrased Vote)

forwarded for public visibility Weitergeleitete Nachricht Betreff:Re: [VOTE] Require Java 21 for Maven 4 (Rephrased Vote) Datum: Wed, 30 Apr 2025 16:02:21 +0200 Von:David Law An: Matthias Bünger -1 Regards, Dave On 30/04/2025 15:12, Matthias Bünger wro

RE: [VOTE] Require Java 21 for Maven 4 (Rephrased Vote)

Non-binding +1 - Jeremy -Original Message- From: Matthias Bünger Sent: Wednesday, April 30, 2025 9:13 AM To: Maven Developers List Cc: us...@maven.apache.org Subject: [VOTE] Require Java 21 for Maven 4 (Rephrased Vote) Hi everyone, over the last years we had several discussions about l

RE: [DISCUSS] Publishing to Central + Maveniverse Njord

FYI regarding deploy plugin I wanted to point out from personal experience on the migration. maven deploy plugin still is used for snapshots per central documentation and I've been doing so for a few weeks now. Here is an existing action that is deploying to new central and still same deploy

Re: [DISCUSS] Publishing to Central + Maveniverse Njord

I think someone should reread the mail :) Yes, many publishing tools have been out there for quite some time, but they are "out of Maven" as you say, and usually they reinvent their own universe as well. But, just like MDK _did integrate_ JReleaser (did you check out MDK?), nothing stops Njord to

Re: [VOTE] Require Java 21 for Maven 4 (Rephrased Vote)

+1 (binding) Thanks! Question to the -1 voters: Please do share a reason for downvotes. I am eager to know why you think we should not update to Java 21. Am Mi., 30. Apr. 2025 um 15:12 Uhr schrieb Matthias Bünger : > > Hi everyone, > over the last years we had several discussions about lifting

Re: [DISCUSS] Publishing to Central + Maveniverse Njord

I think we should also take a look at JReleaser. It has been around quite a while, Andres is an excellent contact and maintainer. Any reason why we should choose one of the two? JReleaser moves the releasing process out of maven, which is a bit sad. But it can be used as a plugin, too. So maybe t

[DISCUSS] Publishing to Central + Maveniverse Njord

Howdy, As we know, we have changes upcoming regarding publishing to central (in short: oss/s01 are being sunset, Central Portal becomes the new service; if unsure what am talking about, please google it up). Also, while there were vendor and third-party plugins and solutions for this, I am talking

Re: [VOTE] Require Java 21 for Maven 4 (Rephrased Vote)

+1 (non-binding) John On 4/30/25 6:12 AM, Matthias Bünger wrote: Therefore, I want to start the official vote to set the minimal Java bytecode target of Maven-Core 4 to 21, meaning Java 21 is required for Maven 4. - To unsu

Re: [VOTE] Require Java 21 for Maven 4 (Rephrased Vote)

+1 Thanks Tamas On Wed, Apr 30, 2025 at 3:12 PM Matthias Bünger wrote: > > Hi everyone, > over the last years we had several discussions about lifting the > required Java version to run Maven from 8 to something higher. You can > find them in the mail archive. > In February 2024 we decided to li

Re: [VOTE] Require Java 21 for Maven 4 (Rephrased Vote)

Hi, +1 from me. Kind regards Karl Heinz Marbaise On 30.04.25 15:12, Matthias Bünger wrote: Hi everyone, over the last years we had several discussions about lifting the required Java version to run Maven from 8 to something higher. You can find them in the mail archive. In February 2024 we d

Re: [VOTE] Require Java 21 for Maven 4 (Rephrased Vote)

+1 (non-binding) - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Require Java 21 for Maven 4 (Rephrased Vote)

Non-binding +1 :) On Wed, Apr 30, 2025 at 3:16 PM Gary Gregory wrote: > Non-binding +1 > > Gary > > On Wed, Apr 30, 2025, 09:12 Matthias Bünger wrote: > > > Hi everyone, > > over the last years we had several discussions about lifting the > > required Java version to run Maven from 8 to somethi

Re: [VOTE] Require Java 21 for Maven 4 (Rephrased Vote)

Non-binding +1 Gary On Wed, Apr 30, 2025, 09:12 Matthias Bünger wrote: > Hi everyone, > over the last years we had several discussions about lifting the > required Java version to run Maven from 8 to something higher. You can > find them in the mail archive. > In February 2024 we decided to lif

[VOTE] Require Java 21 for Maven 4 (Rephrased Vote)

Hi everyone, over the last years we had several discussions about lifting the required Java version to run Maven from 8 to something higher. You can find them in the mail archive. In February 2024 we decided to lift it to 17 (see result: [1*]). An argument to pick 17 instead of 21 was to take

[CANCELED] [VOTE] Require Java 21 for Maven 4

Vote canceled to restart with rephrased vote thread (asked by Tamás) Matthias Am 30.04.2025 um 14:43 schrieb Matthias Bünger: Hi everyone, over the last years we had several discussions about lifting the required Java version to run Maven from 8 to something higher. You can find them in the m

Re: [VOTE] Require Java 21 for Maven 4

+1 good move śr., 30 kwi 2025, 14:44 użytkownik Matthias Bünger napisał: > Hi everyone, > over the last years we had several discussions about lifting the > required Java version to run Maven from 8 to something higher. You can > find them in the mail archive. > In February 2024 we decided to li

Re: [VOTE] Require Java 21 for Maven 4

Howdy, Matthias, you explained why to switch (why to vote +1). But could you reformulate your VOTE thread and ask those voting -1 to EXPLAIN why they voted in such a manner? Thanks T On Wed, Apr 30, 2025 at 2:44 PM Matthias Bünger wrote: > > Hi everyone, > over the last years we had several di

Re: [VOTE] Require Java 21 for Maven 4

-1 On Wed, Apr 30, 2025 at 12:45 PM Matthias Bünger wrote: > > Hi everyone, > over the last years we had several discussions about lifting the > required Java version to run Maven from 8 to something higher. You can > find them in the mail archive. > In February 2024 we decided to lift it to 17 (

[VOTE] Require Java 21 for Maven 4

Hi everyone, over the last years we had several discussions about lifting the required Java version to run Maven from 8 to something higher. You can find them in the mail archive. In February 2024 we decided to lift it to 17 (see result: [1*]). An argument to pick 17 instead of 21 was to take