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 ba
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 particu
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, langu
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 particu
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,
be
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
Indeed you are right! It seems the bootclasspath is set to the runtime
classpath, that means the Java 21 syntax elements would be available in
the editor, but the new API won't.
Oh, so many things to do...
On 12/4/23 16:41, Ernie Rael wrote:
Thanks for the discussion Laszlo,
After reading yo
Thanks for the discussion Laszlo,
After reading your post (more than once) I tried a variety of different
things, including settings the toolchain version to "21" and also
"options.release = 21" for the hell of it.
gradleproject1:lib > properties > Sources > Source/Binary Format
is 21. Wh
Well, the rapid changes of Java put pressure on the tool platforms, and
JVM based languages. That makes our life more difficult.
As of NetBeans, it was quite a fight to move away from Java 8 as a
runtime platform. That does not mean that NetBeans does not support
Java 8 any more, rather, that
gradle 8.4 release notes:
> Java 21 is now supported for compiling, testing, and running such
projects.
gradle 8.5 release notes:
> Gradle now supports running on Java 21.
(I fell for it too the first time I read it, Gradle 8.4 can not run on
Java 21)
-mbien
On 04.12.23 02:20, Erni
On 23/12/03 3:51 PM, Laszlo Kishalmi wrote:
Well, unfortunately gradle init only supports java version
specification since Gradle 8.5
NB20 is bundled with Gradle 8.4.
The gradle 8.4 release notes say
"Java 21 is now supported"
if that matters.
There is a bit workaround needed to run J
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:
> W
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.
Fr
13 matches
Mail list logo
