Path: csiph.com!weretis.net!feeder8.news.weretis.net!newsfeed.xs3.de!news.samoylyk.net!gothmog.csi.it!bofh.it!news.nic.it!robomod From: sre4ever@free.fr Newsgroups: linux.debian.maint.java Subject: Re: gradle reboot Date: Fri, 29 Nov 2024 12:50:01 +0100 Message-ID: References: X-Original-To: Emmanuel Bourg X-Mailbox-Line: From debian-java-request@lists.debian.org Fri Nov 29 11:40:54 2024 Old-Return-Path: X-Amavis-Spam-Status: No, score=-7.199 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] 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/23546 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/a5b057bd2e4eb3bf6cfab6f4bfaed69c@free.fr Approved: robomod@news.nic.it Lines: 27 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: debian-java@lists.debian.org X-Original-Date: Fri, 29 Nov 2024 12:40:36 +0100 X-Original-Message-ID: X-Original-References: <78a8c1b6-c034-7e27-a0fa-9558adfcdfa9@free.fr> <1f8b8ba84612d8e1025cd32ef04c229936fdd117.camel@debian.org> <38d246ff-fac0-e6fd-d602-55f3a12e9751@apache.org> Xref: csiph.com linux.debian.maint.java:12839 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