Howdy,
Maven UA is created like this:
https://github.com/apache/maven/blob/master/maven-core/src/main/java/org/apache/maven/internal/aether/DefaultRepositorySystemSessionFactory.java#L555
I was hoping also for a list of "Apache Maven ..." lines with occurrence
count.
Now am unsure, for example i
as discussed on the "Java version for Maven" thread(s), enablers are key IMHO
on plugins system requirements history, we started with
https://issues.apache.org/jira/browse/MPLUGIN-400
we need to fill data on every Maven -project plugin:
https://ci-maven.apache.org/job/Maven/job/maven-box/job/mave
Do you have maven version and java version at the same time report? I
wonder if old maven is used with old JDK :)
On Wed, Feb 21, 2024 at 23:23 Brian Fox wrote:
> Hi everyone. I haven't caught up on this thread but Tamas pinged me to get
> some usage data from Central. Attached are the Maven ver
I added a piece of information: OpenJDK releases are currently pointed
to the vendor's binary address.
For example, OpenJDK17 Latest Release
(https://wiki.openjdk.org/display/JDKUpdates/JDK+17u), it points to
https://github.com/adoptium/temurin17-binaries/releases/tag/jdk-17.0.10%2B7
Tamás Cserven
Thanks for sharing!
On Wed, Feb 21, 2024 at 11:23 PM Brian Fox wrote:
> Hi everyone. I haven't caught up on this thread but Tamas pinged me to get
> some usage data from Central. Attached are the Maven versions and JDK
> Version counts as reported by User Agent by distinct IP for the last 30
> d
Hi everyone. I haven't caught up on this thread but Tamas pinged me to get
some usage data from Central. Attached are the Maven versions and JDK
Version counts as reported by User Agent by distinct IP for the last 30
days:
On Wed, Feb 21, 2024 at 4:15 PM Hunter C Payne
wrote:
> I also want
I also want to stress that we care about what maven supports far more than
what it requires to build. If it needs JDK 17 to build but the jars are
compliant with Java 8, that's fine with me.
Hunter
On Wednesday, February 21, 2024 at 12:47:33 PM PST, Romain Manni-Bucau
wrote:
Hmm, n
Romain,
1) please do not talk nonsense (about dropping toolchains), as this thread
is unrelated to it (and is not gonna happen)
2) your PDF... did you _read it_? Do you really expect volunteers to
support companies WHO PAY for Java8 (to some third party, like Azul) to
support their business for fr
Hmm, not sure im ready for a 200M vanilla build tool even if it would have
been ok legally...
Le mer. 21 févr. 2024 à 21:41, Hunter C Payne
a écrit :
> I might be wrong but I understood that shipping the JRE/JVM required a
> license and this is why most people don't ship with a JVM bundled. Bu
I might be wrong but I understood that shipping the JRE/JVM required a license
and this is why most people don't ship with a JVM bundled. But perhaps that
has changed since the Oracle v Google/Alphabet trial.
Hunter
On Wednesday, February 21, 2024 at 12:00:54 PM PST, Benjamin Marwell
wro
FWIW, bazel changed its runtime requirement to Java 21.
But they are shipping their own Java Runtime, so their users won't notice. [1]
I think they are the first build tool to do that.
I say this as a FYI fact only, not implying anything.
Make of it what you want.
- Ben
Am Di., 20. Feb. 2024 um
On Wed, Feb 21, 2024 at 7:40 AM Hervé Boutemy wrote:
>
> for sure, given the JDK almanach https://javaalmanac.io/jdk/ , we'll have to
> update our plans https://maven.apache.org/developers/compatibility-plan.html
>
Not sure where this comes from. There's no one EOL date for any
version. It depen
Le mer. 21 févr. 2024 à 10:40, Xeno Amess a écrit :
> Hi.
> I use toolchain for multi-release-jars
> please don't drop it or provide another way for building multi release jars
>
I assume you mean compiler plugin, good news is that it is built-in and
named executable:
https://maven.apache.org/pl
Le 2024-02-21 à 10 h 40, Xeno Amess a écrit :
I use toolchain for multi-release-jars please don't drop it or provide
another way for building multi release jars
I hope to make a proposal as a side-effect of a "Module Source
Hierarchy" proposal, when we will reach that point (after control on
Hi.
I use toolchain for multi-release-jars
please don't drop it or provide another way for building multi release jars
From: Romain Manni-Bucau
Sent: Wednesday, February 21, 2024 3:48:43 PM
To: Maven Developers List
Subject: Re: [DISCUSS] Java version for Maven
H
Le mer. 21 févr. 2024 à 09:07, Hervé Boutemy a
écrit :
> ok, you want to contribute on decoupling JDK of Maven vs JDK of compiler
> and
> tests: perhaps we'll need to open a separate discussion to avoid hijacking
> the
> global plan, but let's have one roundtrip
>
Just to clarify: I don't want b
ok, you want to contribute on decoupling JDK of Maven vs JDK of compiler and
tests: perhaps we'll need to open a separate discussion to avoid hijacking the
global plan, but let's have one roundtrip
scenario is: I use JDK 21 to run Maven, but I need JDK 8 to run my unit and
integration tests
of
I just wanted to note that it is not true that no one is using
toolchains, maybe maven devs don't do it ;-)
e.g. github java setup action supports toolchains:
https://github.com/actions/setup-java
and it was added because many users asked for it / requested it.
For me toolchains become *less
18 matches
Mail list logo
