Re: gradle reboot -- 2025W10 update

Hi Julien,

On 07/03/2025 18:39, Julien Plissonneau Duquène wrote:
> Good evening,
> 
> The FrankenKotlin experiment is now over, and it failed.
> 
> This wasn't as bad as it looked like actually: it was caused by the 
> Kotlin compiler using the default JDK (21) as its target for API 
> compatibility, so while the bytecode was compatible with Java 8 it used 
> some API calls that were introduced in later JDKs instead of 
> reimplementing them as inline code. Using the JDK 11 again solved that 
> for the purpose of using that compiler for building Gradle.

Did you consider rebuilding the packages with Java 8 since we still have 
openjdk-8 in sid? We may even clone the gradle package to make a Java 8 
compatible version if that helps. Same thing with kotlin.


> This outcome is a bit frustrating but it was the most likely one, and I 
> learned a few valuable things in the process.

The simple fact you didn't end in the local hospital after banging your 
head on the wall for so long is quite an achievement!


> My plan is now to update the Kotlin package to 2.0.21 (renaming it 
> kotlin2.0) and use it to build Gradle 8. I'm not sure that both package 
> (and dependencies) will be in a releasable shape in time for Trixie, but 
> if they miss the deadline they can still be made available later through 
> backports.

Yes it's too late for Trixie.

Emmanuel Bourg