Re: gradle reboot
Hi Emmanuel,
Le 2024-11-29 11:42, Emmanuel Bourg a écrit :
Markus raises a good point, I would add that if there is a risk at some
point of breaking the existing packages after upgrading a dependency,
then introducing a new package for the updated dependency is the way to
go. We can deduplicate the dependencies later when the transition to
the newer Gradle is complete.
Or maybe we can keep all of them in experimental for a while, and
duplicate only those that prove (or are suspected eventually, after
discussing that) to be problematic? I would rather keep things as
straightforward as possible with the dependencies, gradle has a lot of
dependencies but several of them only have very few reverse-dependencies
other than gradle and sometimes kotlin.
By the way, any opinion about making that new gradle a "gradle8" package
that provides "gradle"? My feeling is that maintaining up to 3 major
versions of Gradle is probably going to be necessary, given the breaking
changes with every major release (and sometimes in between) and what's
already announced for future releases.
Cheers,
--
Julien Plissonneau Duquène
Reply to: