Good evening,
I have some more good news to share this week:
Le 2024-12-20 19:15, Julien Plissonneau Duquène a écrit :
narrowed down the issue to some subtle failure in class resolution that
could happen either in Kotlin code or in libintellij-core-java or both
It turned out to be some code missing in libmaven-resolver-1.6-java [1]
which also breaks the builds of a few other packages. After solving that
it was surprisingly easy to get Kotlin 1.3.31 to build with some
additional code backported from 1.3.50 (no additional patching
required), and even more surprising to see the Gradle 8.11.1 build
succeed on the second try only after this enhanced Kotlin was installed
and a single-line-change patch added to the Gradle packaging. A
milestone is reached.
Now building is one thing, getting the result to actually work is
another battle. The first attempts could not even run successfully
`gradle --help`, and I'm currently trying to get `gradle :help` to work
within its own project [2], which means improving and fixing some
earlier patching to ultimately get the generated `gradle` to be able to
rebuild itself, and right after that make it build new releases of
Groovy and Kotlin.
Next week I plan to continue to progress on this, and also fork the
`kryo` and `native-plaforms` packages to make it possible to install
both the old and the new versions on a system, and change Gradle 4.4.1
packaging to make it use the old versions (mostly the same scheme as the
current Maven upgrade).
Cheers,
[1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1091772
[2]:
https://salsa.debian.org/jpd/gradle/-/blob/upgrade-to-8.11.1-wip/debian/wip/README.md
--
Julien Plissonneau Duquène
