Path: csiph.com!news.samoylyk.net!gothmog.csi.it!bofh.it!news.nic.it!robomod
From: Emmanuel Bourg <ebourg@apache.org>
Newsgroups: linux.debian.maint.java
Subject: Re: gradle reboot
Date: Fri, 29 Nov 2024 11:50:01 +0100
Message-ID: <JO6Jr-crX8-5@gated-at.bofh.it>
References: <JJqpr-9klD-5@gated-at.bofh.it> <JN3DX-bLiV-1@gated-at.bofh.it>
Old-Return-Path: <ebourg@apache.org>
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.15.1
Content-Language: en-US
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Approved: robomod@news.nic.it
Lines: 17
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
Xref: csiph.com linux.debian.maint.java:12837

Le 26/11/2024 à 14:09, Markus Koschany a écrit :

> I discarded the idea to upgrade Gradle to 6.x or even newer releases because
> the main problem with Gradle for Debian is the complex interaction between its
> (build)-dependencies. Since we only support one version of a library in
> general, you will quickly reach a point where you are stuck in a loop between
> upgrading existing Debian packages, then fixing broken reverse-dependencies,
> and then moving on to build Gradle offline. And for me those iterations never
> seemed to end.

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.

Emmanuel Bourg