Re: Build cache extension release

I've resolved conflicts and merged https://github.com/apache/maven-build-cache-extension/pull/34 Le jeu. 1 juin 2023 à 07:27, Olivier Lamy a écrit : > Hi, > I'd like to release the build cache extension in the coming days. > If someone has something to merge or fix please let me know/ > > cheers

Re: Question - JDK Minimum of future Apache Maven 4.0.0

Sounds like a plan to me we have to adopt the new JDK release schedule somehow anyway, we cant stick on java 8 now it is EOL and java 11 soon so today only java 17 is a fair option for users. Romain Manni-Bucau @rmannibucau | Blog

Re: Question - JDK Minimum of future Apache Maven 4.0.0

JDK 8 active support ended 15 months ago, so I think that's definitely fine to require a newer version. I don't think we should wait and support JDK 8 until 2030 and then switch from JDK 8 to what, JDK 24 ? That's really not a good plan imho and that's what maintenance branches are used for. The J

Build cache extension release

Hi, I'd like to release the build cache extension in the coming days. If someone has something to merge or fix please let me know/ cheers Olivier - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands,

Re: Question - JDK Minimum of future Apache Maven 4.0.0

+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.

Re: [VOTE] Release Apache Maven Release Plugin version 3.0.1

+1 Le mar. 30 mai 2023 à 23:35, Slawomir Jaranowski a écrit : > Hi, > > We solved 8 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824&version=12353136 > > There are still a couple of issues left in JIRA: > > https://issues.apache.org/jira/issues/?jql=project%2

Re: [VOTE] Release Maven Project Info Reports Plugin version 3.4.4

Please take care of all open JIRA issues which you have already merged. On 2023/05/26 19:47:38 Elliotte Rusty Harold wrote: > There's some dependency cleanup that could be done in this project. a > couple of artifacts should be test scope and also updated to the > latest versions, perhaps a few ot

Re: Question - JDK Minimum of future Apache Maven 4.0.0

I also would like to point out that OpenJDK 8 support will surpass 11 by 2030: https://endoflife.date/java - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Release Apache Maven Release Plugin version 3.0.1

Renovate is a better alternative to dependabot and usually finds items deeper in builds such as IT tests with basically zero config and a nice issue tracker right on github showing full content of repo, anything team declined, etc. If you happen to check out mybatis repos, you can see it in act

Re: Question - JDK Minimum of future Apache Maven 4.0.0

Hi all, >From my perspective having Java 17 as the minimal runtime for maven itself is fine. I have several projects that need to produce Java 8 binaries and I have been running all my builds with Java 17 for quite some time now. The toolchains setup works fine for all use cases I have seen so far

Re: Question - JDK Minimum of future Apache Maven 4.0.0

That one needs java to *RUN* maven is an implementation detail for me and the actual java version do not matter. At best maven would ship with whatever JVM is required, or has a launcher that downloads one or ... e.g. for Eclipse IDE (and other software as well) one simply downloads a package

Re: Question - JDK Minimum of future Apache Maven 4.0.0

These are JDKs used as "Module JDK". These are JDKs that compile the source code or run the tests (as the default option). Regardless of the language level setting. So the first line reads like this: "Among IntelliJ Ultimate users with Maven projects, 49.1% have at least one module that is compile

Re: GH issues and GH discussions

Hi all, I really like GH issues and discussions ... they lower the bar for contribution quite a bit and feel a lot more inviting for newer contributors. At least have we seen a significant increase in contributions since we switched to GH Issues and are currently starting to use GH Discussions

Re: Question - JDK Minimum of future Apache Maven 4.0.0

Thank you! But I have a problem understanding this info AFAIK, IDEA embeds Java "that runs on". So what is this, targeted platforms? (like maven.compiler.release?) Or JDKs registered in IDE used for projects? Thanks T On Wed, May 31, 2023 at 4:00 PM Nikita Skvortsov wrote: > > sure, it woul

Re: Question - JDK Minimum of future Apache Maven 4.0.0

> sure, it would be nice to see those numbers... :) Here we go. The numbers below are for users who have Maven projects. Please note that the same user can report multiple JDKs, so numbers do not add up to 100. For IntelliJ Ultimate, the Top 5 JDK versions are: 8 - 49.1% 17 - 37.4% 11 - 27.2% 20

Re: Question - JDK Minimum of future Apache Maven 4.0.0

Think whatever version we release we must meet the most common version for project starting when release is around, as of today - and even in a year - it will not be 21 but 17 AFAIK so 17 looks natural if we intend to have a 4.0.0 < 2 yearselse 21 is very relevant. Anything else goes legacy on

Re: Question - JDK Minimum of future Apache Maven 4.0.0

Good question! :D On Wed, May 31, 2023 at 2:34 PM Delany wrote: > Excuse my ignorance but what do customer requirements have to do with the > build tool's required JDK? > Delany > > > On Wed, 31 May 2023 at 13:57, Elliotte Rusty Harold > wrote: > > > On Wed, May 31, 2023 at 8:30 AM Guillaume N

Re: Question - JDK Minimum of future Apache Maven 4.0.0

(Non-binding chatter) I'm ok with Java 17 but since M4 feels like it's not around the corner, why not go for Java 21-EA and possibly learn even more cool tech. Surely Java 21 which is an LTS version will be released as GA before M4. Gary On Wed, May 31, 2023, 04:30 Guillaume Nodet wrote: > I'd

Re: Question - JDK Minimum of future Apache Maven 4.0.0

Excuse my ignorance but what do customer requirements have to do with the build tool's required JDK? Delany On Wed, 31 May 2023 at 13:57, Elliotte Rusty Harold wrote: > On Wed, May 31, 2023 at 8:30 AM Guillaume Nodet wrote: > > > I think with those improvements, requiring JDK 17 for master sho

Re: Question - JDK Minimum of future Apache Maven 4.0.0

Howdy Nikita, sure, it would be nice to see those numbers... :) Thanks Tamas On Wed, May 31, 2023 at 2:25 PM Nikita Skvortsov wrote: > > Do we have some download stats (not a poll) - maybe on sdkman or some jdk > > vendors side? > > Dear Maven team, > > Would it help you to make the decision i

Re: Question - JDK Minimum of future Apache Maven 4.0.0

On Wed, May 31, 2023 at 1:59 PM Elliotte Rusty Harold wrote: > That's not really true. Short of a complete fork, new versions can't > go out without effort from PMC members. Users cannot effectively > self-serve here. > That's not what Guillaume said. Nobody mentioned "self serve". Simply put, a

Re: Question - JDK Minimum of future Apache Maven 4.0.0

> Do we have some download stats (not a poll) - maybe on sdkman or some jdk > vendors side? Dear Maven team, Would it help you to make the decision if you have usage statistics of JDK 17 among IntelliJ IDEA Maven users? -- Nikita Skvortsov Software Developer JetBrains http://www.jetbrains.com T

Re: Question - JDK Minimum of future Apache Maven 4.0.0

On Wed, May 31, 2023 at 10:37 AM Guillaume Nodet wrote: > > Who said so ? If there's a need and will to maintain the 3.x branch, so be > it. No one is forbidden to work on those branches. That's not really true. Short of a complete fork, new versions can't go out without effort from PMC member

Re: Question - JDK Minimum of future Apache Maven 4.0.0

On Wed, May 31, 2023 at 8:30 AM Guillaume Nodet wrote: > I think with those improvements, requiring JDK 17 for master should be > doable. Any concerns of suggestions ? Hard no from me. JDK 8 is still very much in use, and is my day-to-day VM. I switch to 11 when I have to, and I don't anticipat

Re: [VOTE] Release Apache Maven Release Plugin version 3.0.1

FYI, there seem to be some issues with dependabot configs. It's useful when it fires, but it doesn't always, and sometimes it closes update PRs for no valid reason I can discern. And of course there are the more complex updates that can require more than a simple number change in a pom.xml like ht

Re: [VOTE] Release Apache Maven Release Plugin version 3.0.1

Common thread I keep seeing. Update all the libraries! ...the common thread.. No concern on this one but maven does still release vulnerable plugin usage especially around transient commons collections. We keep patching so it's also frustrating the speed of plugin releases that are not acco

Re: [HEADS UP] Upcoming Resolver and Maven releases

Henning, This intent of all threads (the "[HEADS UP]") that I have been creating since the 3.9.0 release was actually meant as a communication effort to users not on ML (btw, see related comm related discussions). What I usually do is copy the ponymail URL of the thread and post it on twitter or m

Re: Question - JDK Minimum of future Apache Maven 4.0.0

+1 on java 17. Stats matter but can tell you we are 90% jdk 17 on builds already, don't use toolchains. It's unnecessary. A lot of it is education to development staff that Devops must push and enable teams. Maven could help drive that here... As to comment on 3.8 vs 3.9. We already dropped

Re: [VOTE] Release Apache Maven Release Plugin version 3.0.1

One minor dependency update to maven-scm: https://github.com/apache/maven-release/pull/192 Otherwise, looks good. On Tue, May 30, 2023 at 9:35 PM Slawomir Jaranowski wrote: > > Hi, > > We solved 8 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824&version=1235313

Re: Question - JDK Minimum of future Apache Maven 4.0.0

Le mer. 31 mai 2023 à 12:28, Michael Osipov a écrit : > On 2023/05/31 10:03:34 Guillaume Nodet wrote: > > Le mer. 31 mai 2023 à 11:21, Michael Osipov a > écrit : > > > > > > I think with those improvements, requiring JDK 17 for master should > be > > > > doable. Any concerns of suggestions ? >

Re: Question - JDK Minimum of future Apache Maven 4.0.0

On 2023/05/31 10:03:34 Guillaume Nodet wrote: > Le mer. 31 mai 2023 à 11:21, Michael Osipov a écrit : > > > > I think with those improvements, requiring JDK 17 for master should be > > > doable. Any concerns of suggestions ? > > > > I am against this. There are enough people who cannot move to J

Re: Question - JDK Minimum of future Apache Maven 4.0.0

On Wed, May 31, 2023 at 11:22 AM Michael Osipov wrote: > I am against this. There are enough people who cannot move to Java 17 for > a plethora of reasons regardless of Toolchains support. We provide a low > level tool and it should have a low barrier to use. Maven 4 should be used > as a transit

Re: Question - JDK Minimum of future Apache Maven 4.0.0

On 31/05/2023 at 9:21:43 PM, Michael Osipov wrote: > even if we are in alpha phase now. > I bet many people will stick for 3.9.x or even 3.8.x for the years to > come. Yep - unless 4.x can introduce some hook for extensions to modify the POM model before becoming immutable, I don’t see us movi

Re: Question - JDK Minimum of future Apache Maven 4.0.0

Le mer. 31 mai 2023 à 11:21, Michael Osipov a écrit : > > I think with those improvements, requiring JDK 17 for master should be > > doable. Any concerns of suggestions ? > > I am against this. There are enough people who cannot move to Java 17 for > a plethora of reasons regardless of Toolchain

Re: Question - JDK Minimum of future Apache Maven 4.0.0

+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 lo

Re: Question - JDK Minimum of future Apache Maven 4.0.0

Do we have some download stats (not a poll) - maybe on sdkman or some jdk vendors side? Recently I saw (with customers I'm working on) the java 17 adoption being quite large and since people stucked to 3.9 will be covered for java 8 I think it could be sane to switch *master* if we can validate wit

Re: Question - JDK Minimum of future Apache Maven 4.0.0

> I think with those improvements, requiring JDK 17 for master should be > doable. Any concerns of suggestions ? I am against this. There are enough people who cannot move to Java 17 for a plethora of reasons regardless of Toolchains support. We provide a low level tool and it should have a low

Re: [VOTE] Release Apache Maven Release Plugin version 3.0.1

+1 On Tue, May 30, 2023 at 11:35 PM Slawomir Jaranowski wrote: > Hi, > > We solved 8 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824&version=12353136 > > There are still a couple of issues left in JIRA: > > https://issues.apache.org/jira/issues/?jql=project%

Re: [VOTE] Release Apache Maven Release Plugin version 3.0.1

+1 - tested on macOS using Maven 3.9.2 with a custom release strategy. Maarten On 30/05/2023 23:34, Slawomir Jaranowski wrote: Hi, We solved 8 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824&version=12353136 There are still a couple of issues left in JIRA: h

Re: Question - JDK Minimum of future Apache Maven 4.0.0

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 modif

Re: [VOTE] Release Apache Maven Release Plugin version 3.0.1

+1 wt., 30 maj 2023, 23:35 użytkownik Slawomir Jaranowski < s.jaranow...@gmail.com> napisał: > Hi, > > We solved 8 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824&version=12353136 > > There are still a couple of issues left in JIRA: > > https://issues.apache.

Re: [VOTE] Release Apache Maven Release Plugin version 3.0.1

+1 Reproducible Builds ok: reference build done with JDK 17 on *nix Regards, Hervé On 2023/05/30 21:34:37 Slawomir Jaranowski wrote: > Hi, > > We solved 8 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824&version=12353136 > > There are still a couple of issue

Re: [HEADS UP] Upcoming Resolver and Maven releases

Hi, With validation=summary when only EXTERNAL issue are presents we have: [WARNING] [WARNING] Plugin [INTERNAL] validation issues were detected in following plugin(s) [WARNING] [WARNING] [WARNING] For more or less details, use 'maven.plugin.validation' property with one of the values (case insen