On 2/26/24 11:42 AM, Basil Crow wrote:
We had a similar conversation in the Jenkins community, and I wrote up
our conclusions here:
We also had a similar conversation in the NetBeans community, with the
final vote to drop JDK 8 (vote result: 20 to 1.5). See here:
[VOTE][RESULT] Minimum JDK b
+1 (set JDK17 min version for Maven 4.x)
Secretly hoping it ends up being JDK 21 (or an even later LTS),
John
On 2/27/24 11:30 PM, Benjamin Marwell wrote:
Hi Maven Devs/Users/Committers and PMC members!
After several discussions on the mailing lists, I would like to
start a vote in favour of s
Maven 3.9.7 fails to set a profile property in the main JavaFX POM:
Maven Central: org.openjfx:javafx:22.0.1
https://central.sonatype.com/artifact/org.openjfx/javafx/22.0.1
Building a simple JavaFX program with Maven 3.9.6 or 3.8.8 works fine,
but I get the following error when I upgrade to Mav
Thank you for the quick response, Tamás.
On 5/27/24 11:51 AM, Tamás Cservenák wrote:
Can you create a small reproducer, ideally shared on github or similar
service?
This "Hello World" JavaFX project illustrates the problem for me:
Hello JavaFX!
https://github.com/jgneff/hello-javafx
Just
On 5/28/24 7:52 AM, Tamás Cservenák wrote:
well, after a quite long investigation we came to several conclusions:
* 3.9.6 and before worked really "by chance", as
* the POM is invalid
Thank you very much, Tamás and Romain. I really appreciate your help and
expertise. I will report the issue to
-1
I'm getting the following error when I run Maven 3.9.9 in a directory
that does not have a ".mvn" sub-directory. Does anyone else get these
errors?
.../maven/bin/mvn: 136: [: /home/john: unexpected operator
.../maven/bin/mvn: 136: [: /home: unexpected operator
.../maven/bin/mvn: 136:
I think the errors I'm getting in my previous message are from Maven
3.9.9 using a Bash construct in a normal '/bin/sh' shell script, which
is dash on my Ubuntu system.
Dash prints the "unexpected operator" error message when '==' is used
instead of '=' in a test. I think you can also use '-eq
Thank you, Tamás. Respin #1 is working fine for me now.
John
On 8/14/24 1:32 AM, Tamás Cservenák wrote:
Howdy,
Thanks for testing! Fix is on way (3.9.9 and 4) and will respin 3.9.9
release:
https://github.com/apache/maven/pull/1652
https://github.com/apache/maven/pull/1653
Thanks
T
On 9/25/24 7:23 AM, Jorge Solórzano wrote:
* Using the SCM last commit date is a bad choice, not everyone will use SCM
or the source code could be downloaded without scm information (eg.: Source
Code download links from GitHub), so this is a -1 for me.
That makes sense, but in general, I always
A follow-up message for those not familiar with the SOURCE_DATE_EPOCH
environment variable ...
On 9/25/24 9:22 AM, John Neffenger wrote:
That makes sense, but in general, I always set the date like this:
SOURCE_DATE_EPOCH=$(git log -1 --pretty=%ct)
export SOURCE_DATE_EPOCH
I pass that
+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
I'm genuinely curious, is there a reason why Maven has not switched to
fixed release dates and Java support policies?
Every other Java project in which I participate, including the JDK
itself, JavaFX, and NetBeans, switched long ago to predetermined release
dates and Java versions. For any of
On 7/11/25 7:26 AM, Calum Harrison wrote:
"Trusted Checksums" is good to know about -- I had missed that.
It's very easy to miss!
I came across it accidentally myself rather recently. I was
participating in this issue:
[MNG-6026] Extend the Project Object Model (POM) with trust information
13 matches
Mail list logo
