Hi Owen,
On Wed, 2023-12-06 at 14:01 +1100, Owen Thomas wrote:
> I might use Maven in the future, and I'll hang on to my gradle build at the
> moment (I'm getting incompatibility errors in my build but these don't seem
> to have a material influence on what is being built), but I may yet turn
On Wed, 6 Dec 2023 at 10:38, Andreas Reichel
wrote:
> 1) dependency resolution (including the understanding, what Class format
> the artifact is providing)
> 2) compiling and packaging based on the built classpath
>
> For 2), any Gradle will do.
> But for 1) Gradle needs to understand the
On 06.12.23 00:32, Owen Thomas wrote:
This matrix is just doing my head in, because all I can gather from
the page disclosed is a mechanism - I don't understand why the
mechanism needs to exist in the first place.
because gradle uses kotlin and groovy as the config file format
language,
Owen,
from what I understand, Gradle solves 2 different tasks:
1) dependency resolution (including the understanding, what Class
format the artifact is providing)
2) compiling and packaging based on the built classpath
For 2), any Gradle will do.
But for 1) Gradle needs to understand the
Thanks for that; Maybe I'm not keeping enough attention to what is going on
here to really make a constructive comment, butI was looking more for
justification of the existence of this "compatibility matrix" and Gradle's
future intentions in supporting Java. This matrix is just doing my head in,
https://docs.gradle.org/current/userguide/compatibility.html
On 04.12.23 01:24, Owen Thomas wrote:
Is there a page I can read that outlines how Gradle will work with
Java in the future? This stuff is giving me a headache.
OpenPGP_signature.asc
Description: OpenPGP digital signature
projects with Gradle.
I can run the project tests with no workaround.
Also, I manually set the gradle version for the project to 8.5
./gradlew wrapper --gradle-version 8.5
The problem icon is still there and the message says
"Java version: 21 ... not supported by Gradle 8.5"
Bot
ere is a bit workaround needed to run Java 21 projects with Gradle.
I can run the project tests with no workaround.
Also, I manually set the gradle version for the project to 8.5
./gradlew wrapper --gradle-version 8.5
The problem icon is still there and the message says
"Java version
"Java version: 21 ... not supported by Gradle 8.5"
Both 8.4 and 8.5 claim to support JDK-21. This all makes no sense.
I think (I don't remember) that I could run the project tests when it
was gradle 8.4 as well with no workaround.
This all makes me wonder if there's something hardcode
a bit workaround needed to run Java 21 projects with Gradle.
I can run the project tests with no workaround.
Also, I manually set the gradle version for the project to 8.5
./gradlew wrapper --gradle-version 8.5
The problem icon is still there and the message says
"Java version:
ded to run Java 21 projects with Gradle.
I can run the project tests with no workaround.
Also, I manually set the gradle version for the project to 8.5
./gradlew wrapper --gradle-version 8.5
The problem icon is still there and the message says
"Java version: 21 ... not supporte
What's going on with Java and Gradle? Would I be right in supposing that it
would be simpler just to go back to Ant?
Is there a page I can read that outlines how Gradle will work with Java in
the future? This stuff is giving me a headache.
On Mon, 4 Dec 2023 at 10:51, Laszlo Kishalmi
wrote:
>
Well, unfortunately gradle init only supports java version specification
since Gradle 8.5
NB20 is bundled with Gradle 8.4.
There is a bit workaround needed to run Java 21 projects with Gradle.
Set the Java Runtime version for Gradle in Tools > Options > Java >
Gradle to Java 20 or below.
Running NB-20, jdk21.
The goal is to play with some JDK-21 APIs...
Creating a project using NB's "New Project > Java with Gradle".
I can build and run the default "Library" and test. But there's the
warning icon and "Resolve Project Problems".
Any way to get rid of the warning?
-ernie
14 matches
Mail list logo
