well I just doubt.
From: Xeno Amess
Sent: Tuesday, February 6, 2024 12:18:42 PM
To: Maven Developers List
Subject: Re: Java version for Maven 4?
well nothing affensive but do any guys got any payments from those still-java-6
companies for maintaining maven for t
well nothing affensive but do any guys got any payments from those still-java-6
companies for maintaining maven for them？
From: Gary Gregory
Sent: Tuesday, February 6, 2024 6:14:32 AM
To: Maven Developers List
Subject: Re: Java version for Maven 4?
An interestin
An interesting question for me is whether we need to think about companies
that pay for old JDK support and how that affects our support for these old
JDKs.
Gary
On Mon, Feb 5, 2024, 4:28 PM Elliotte Rusty Harold
wrote:
> On Mon, Feb 5, 2024 at 2:22 PM Romain Manni-Bucau
> wrote:
> >
> > Hi El
On Mon, Feb 5, 2024 at 2:22 PM Romain Manni-Bucau wrote:
>
> Hi Elliotte,
> Java 11 support is already EOL for most vendor until you go "premium"
> flavor which will likely be very few people and most of them will be able
> to pay somebody to backport the needed stuff in custom distro of their wo
> I get the impression that folks who haven't worked in such large
> mono-repos aren't aware of just how big a multi-year effort it is to
> move a repo like that onto a new JDK version. And that's just the VM,
> even before you allow devs to change the language level and start
> using the new featu
Howdy,
and sorry, I could not hold my breath...
Basically, you talk about some project somewhere that has been built with
Maven3 for the past 10 years. Fine: You can continue building it using the
same Maven3 for another 10 years, nothing stops you. But I see really
nothing, but really nothing th
Hi Elliotte,
While I share the wish 1 repo = 1 JDK, I have a hard time to see how any
company - including the ones you cite - can seriously bet on Java 11 today
for the future (not saying it wasnt hard to reach Java 11 today but we are
discussing on what we'll do tomorrow) and why it would pushbac
Based on my experience, I think we (FOSS developers) can create our own
momentum by "simply" creating an EOL schedule. I have seen this EOL aspect
motivate the move away from Jetty 9 for example. Since Maven 4 is not out,
there is nothing to EOL in Maven 3 land unless you want to say that only
3.9.
On Mon, Feb 5, 2024 at 12:01 PM Benjamin Marwell wrote:
> Why 17? 11 is often earlier EOL'd than 8 and 17, so I see absolutely
> no advantage of going to 11:
>
The advantage of going with 11 instead of 17 is that at least 2 really
big tech companies I could name (and who you can probably guess f
Those who need Java 8 to *run* Maven will probably not upgrade to
Maven 4 anyway, as their builds will have other problems preventing
them from upgrading.
A few third-party plugins already moved to Java 11+, thinking of spotless.
That said:
+1 Stick with 8 for Maven 3.9.x and maybe a 3.10.x (not
Implemented in https://github.com/tisonspieces/os-detector/pull/4.
Best,
tison.
tison 于2024年2月5日周一 21:34写道：
>
> I found Maven Invoker is a component that can be used [1]. Let me try
> to make an example.
>
> Best,
> tison.
>
> [1] https://maven.apache.org/shared/maven-invoker/usage.html
>
> tiso
I found Maven Invoker is a component that can be used [1]. Let me try
to make an example.
Best,
tison.
[1] https://maven.apache.org/shared/maven-invoker/usage.html
tison 于2024年1月25日周四 11:09写道：
>
> Hi,
>
> I'm writing a Mojo with an Extension extending
> AbstractMavenLifecycleParticipant.
>
> No
I vote for kill jdk8 out as to force them upgrade to 11+
From: Tamás Cservenák
Sent: Sunday, February 4, 2024 10:35:55 PM
To: Maven Developers List
Subject: Re: Java version for Maven 4?
Howdy,
See Inline.
On Sun, Feb 4, 2024 at 3:01 PM Elliotte Rusty Harold
w
13 matches
Mail list logo
