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
