Re: gradle reboot -- 2025W08 update

Pierre Gruet <[email protected]> Fri, 21 Feb 2025 19:26:07 +0100
Newsgroups gmane.linux.debian.devel.java
Message-ID <[email protected]>
Hi Julien,

Le 21/02/2025 à 18:15, Julien Plissonneau Duquène a écrit :
> Good evening,
> 
> All hopes to get Gradle 8 to work with the FrankenKotlin are not lost yet.
> 
> Le 2025-02-14 20:02, Julien Plissonneau Duquène a écrit :
>> test if that gradle will rebuild itself by next week, and then either 
>> debug it (probable outcome)
> 
> After finishing to fix Gradle's build the first run of the new binaries 
> was a pleasant surprise as it went straight into lauching its daemon 
> process (I was expecting some fight there), and that one started built- 
> in configuration tasks, compilation of the packaging's init.d Groovy 
> scripts, and then crashed cleanly on compiler errors after attempting to 
> compile the pluginManagement block of the root settings.gradle.kts.
> 
> It then took me several debugging sessions (debugging the bootstrap 
> gradle as well to figure out the expected code path) to narrow down the 
> issue to a missing step in function call resolution. In the process I 
> adjusted the Kotlin compiler configuration in the Gradle DSL plugin and 
> backported a few more minor fixes and features into Kotlin. But I had to 
> give up on my last backport attempt as it appeared that it had a non- 
> trivial dependency on a much larger change set: the Kotlin compiler 
> plugin underwent a significant refactoring for release 1.3.50, and that 
> includes some changes in the way the script compiler is configured.
> 
> For the record, despite requiring Kotlin 2.0.21 the current Gradle 8 
> Kotlin DSL plugin is actually using the (legacy) K1 compiler, and this 
> is among the reasons why I still think there are chances to get it to 
> work with the FrankenKotlin.
> 
> I will now try to backport the whole scripting plugin from Kotlin 1.3.50 
> into our FrankenKotlin and see how it goes, as this backport will bring 
> its code state to something much closer to what it currently looks like 
> in Kotlin 2.0.20. This is probably the last "large" Kotlin backport that 
> I will attempt before declaring that approach to be a dead end.

Thanks for this report and for all your work on Gradle. This is much useful!

> 
> Have a nice week-end,
> 

Same to you,

-- 
Pierre
OpenPGP_signature.asc (application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEM8soQxPpC9J9y0UjYAMWptwndHYFAme4xT8ACgkQYAMWptwn
dHYFow/+LTy85K+aFLwlfzlAf5l+1d2Q3lNFzpd+caL3VlRtpyGXUiLo1Y5HZywQ
H3mq9HdPEl5uMunl7fZ21HzS1tFwSOBr2ipKHiKnURqBsM1OrY6lDFzFGIy3U2ks
G31Ob2aXrcLgKs2/quS8gJLYdXge7TBC3mYX2dxB77WMU2xu6+Kbn0gZEYV9dW+x
KbvkMgN6vYdrk6DtisckLMSa9gJ7GqKvjVkbErXcSNDlZfO/lRU56VVGHF5hu+W0
AQ5aDVEruEcAkZ/4sB5EvSY1iaiqZo+AFQFjpo+CKu5DWtWI0PPZcHyL37MlWA7h
6nWjfMih2B6js9fW6LBmQkSqED+ZMzPTv64dbYpnRjMcJT3BZKPIQ7mVurx6eosP
kS8h0UkvKsGlpKsNHA9uLTSMXZyuRZDITy69dFgJ6Q02XbIH62ei94YukMW0Hep9
ePHiLfJbVe4PS2zryM2FZaf/3jd/eeEG7yVKw+amR9Ba7g0/3RmQoMAyUp18yC7V
TEV27JjLqiIWWtE517EORf0dYWI4zJ8kMB1DLqbXTFn2I0c/qwi4Qf/K5TcNdzHj
NoHMsMrbt3F9f/kBRzAK4dHeBQYkRNl165I5Y+ToSdSGnRrpH4+oZVm+uUa7O7b/
4I0mZT1/RE2zUWh2ebp2zGoJGjpF4WoOz/+J3LQrcVz+mDxSQ+0=
=HGiY
-----END PGP SIGNATURE-----