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

+1 (non binding) Am 30.04.2025 um 15:12 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 mail archive. In February 2024 we decided to lift it to 17 (se

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)

+1 here. And wishing a great day to everyone. Le jeu. 1 mai 2025, 08:24, Grzegorz Grzybek a écrit : > +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 k

Re: [HEADS UP] Maven 3.9.10 release

JAnsi seems like a frequent source of issues like this. Ideally I'd like to get rid of it, but I'm not sure how much effort that would be. On Thu, May 1, 2025 at 3:19 AM Mark Derricutt wrote: > > Tamás, Guillaume - > > I note when running 3.9.9 under Java 24, I see: > > WARNING: A restricted met

Permission to merge?

Hello There is two branches that we could merge, but I would like to double-check on this list before to move ahead. The first pull request (PR) is replacing Plexus dependency by java.nio in the maven-clean-plugin. This PR got two reviewers approval, so in my understanding I could merge, but

Re: [HEADS UP] Maven 3.9.10 release

On Thu, 1 May 2025 at 06:22, 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. It was done

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

+1, libraries will enforce it at some point to be properly functional so better to not start late with first 4.0.0 Romain Manni-Bucau @rmannibucau | .NET Blog | Blog | Old Blog

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: [HEADS UP] Maven 3.9.10 release

On Mon, 28 Apr 2025 at 13:59, Tamás Cservenák wrote: > > Howdy, > > quickly scanned some recent MNG JIRAs, and I think these would be good > candidates as well: > > - https://issues.apache.org/jira/browse/MNG-8685 (limited mode, maybe > only GHA along the lines of original PR?) There is no suppo

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

+1 Tibor Digana 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 lift

Re: Release tag format for Maven projects

Howdy, I don't see why we want to change tag format (!) on existing, especially long time existing and running projects. What gain does it give ASIDE for some tooling nicer output, that we never used before (that generates something out of it)? How to sort history after? How to process tags for so

Re: Release tag format for Maven projects

Explanation: I am talking about some automation that for example uses JGit to get version information and so on... so "sorting on GH UI" is one thing, but automatic processing of tags by various means is completely different. T On Thu, May 1, 2025 at 10:37 PM Tamás Cservenák wrote: > > Howdy, >

Release tag format for Maven projects

Hi, We introduce a short and the same template release tag name for Maven projects as: v@{project.version} in parent 44: https://github.com/apache/maven-parent/pull/455 It will change a tag name on history ... but for me is more modern and simplified other configurations like for release-drafte

Re: [DISCUSS] Publishing to Central + Maveniverse Njord

Hi Jeremy, On 30.04.2025 18:26, Jeremy Landis wrote: Because on a physical release, the deploy plugin is taken over by the central publishing extension and cyclonedx relies on deploy, this flag was necessary `false` for cyclonedx to deploy during release. The CycloneDX Maven Plugin is not t

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

Hi, On 30.04.2025 15:12, Matthias Bünger wrote: In a chat with several PMC, committers and contributors nobody saw strong disadvantages on this. 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.

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

+1 non binding. Bring on the new world! -- "Great artists are extremely selfish and arrogant things" — Steven Wilson, Porcupine Tree On 1 May 2025 at 6:23:47 PM, Grzegorz Grzybek wrote: > +1 (non-binding) > > - JEP 400: UTF-8 by Default (JDK18) > - JEP 418: Internet-Address Resolution SPI (J

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

+1 /Anders (mobile) Den ons 30 apr. 2025 15:12Matthias Bünger skrev: > 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