Path: csiph.com!weretis.net!feeder9.news.weretis.net!newsfeed.endofthelinebbs.com!news.corradoroberto.it!gothmog.csi.it!bofh.it!news.nic.it!robomod From: =?UTF-8?Q?Julien_Plissonneau_Duqu=C3=A8ne?= Newsgroups: linux.debian.maint.java Subject: Re: gradle reboot -- 2025W05 update Date: Fri, 31 Jan 2025 19:10:02 +0100 Message-ID: References: X-Mailbox-Line: From debian-java-request@lists.debian.org Fri Jan 31 18:00:49 2025 Old-Return-Path: X-Amavis-Spam-Status: No, score=-7.195 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, LDO_WHITELIST=-5, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -5.5 MIME-Version: 1.0 User-Agent: Webmail Free/1.6.9 X-Sender: sre4ever@free.fr Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Mailing-List: archive/latest/23623 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/fd7bed1065756d6755c922929c201585@free.fr Approved: robomod@news.nic.it Lines: 36 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Fri, 31 Jan 2025 19:00:32 +0100 X-Original-Message-ID: X-Original-References: <5284bacb294ba1ff08f32a5a0b175dd4@free.fr> <8497785db64c2691266dc8269486d7c2@free.fr> <2ec4a44b89889611d1dfa2ee19129e86@free.fr> <6f53f62c9f3bff92fa66c714d62da6d1@free.fr> <965acdffa651fe10e90e6f26728e4af7@free.fr> <2e2ac5f7efc8ae401863382517249ce9@free.fr> Xref: csiph.com linux.debian.maint.java:12913 Good evening, Some slow progresses were made since Monday towards getting a Gradle build that doesn't depend on pre-built binaries from the upstream Gradle and Kotlin projects. Le 2025-01-27 19:25, Julien Plissonneau Duquène a écrit : > > trying to figure out how to configure the whole thing so the bootstrap > gradle (from upstream, thus unpatched) still finds the Kotlin 2.0.20 > that makes it happy, but builds a gradle that uses our Frankenkotlin. I somehow found my way around this, swapping a dependency on a pre-built Gradle plugin from the previous version to one on the same version as the one being built, and downgrading the Kotlin version to that of our Frankenkotlin. I'm now deep into backporting a plugin and some APIs into that Kotlin, reverse-engineering some of the tedious work that was done by Samyak Jain and Emmanuel Bourg to convert the Kotlin build scripts to Groovy and downgrade them to work with a Gradle that was already quite obsolete, and trying to apply the same recipes to build scripts designed for significantly later versions of both Kotlin and Gradle. I guess that no one will be surprised if I state again that it's a slow and tedious process, though I think I'm progressing, and I still have some hopes to be able to get the thing to work with the Frankenkotlin. Considering the alternative would be to rebootstrap a Kotlin 2+ at the same time, which would be a significant project, I think it's worth investing some time into this. Right now I'm in a train on my way to Brussels, hoping to meet some of you this week-end at the FOSDEM. Cheers, -- Julien Plissonneau Duquène