Groups > linux.debian.maint.java > #12837

Re: gradle reboot

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> (permalink)
References	<JJqpr-9klD-5@gated-at.bofh.it> <JN3DX-bLiV-1@gated-at.bofh.it>
X-Original-To	debian-java@lists.debian.org
X-Mailbox-Line	From debian-java-request@lists.debian.org Fri Nov 29 10:42:19 2024
Old-Return-Path	<ebourg@apache.org>
X-Amavis-Spam-Status	No, score=-14.584 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, LDO_WHITELIST=-5, NICE_REPLY_A=-2.588, RCVD_IN_DNSWL_HI=-5, 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
Authentication-Results	apache.org; auth=none
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
X-Mailing-List	<debian-java@lists.debian.org> archive/latest/23544
List-ID	<debian-java.lists.debian.org>
List-URL	<https://lists.debian.org/debian-java/>
List-Archive	https://lists.debian.org/msgid-search/38d246ff-fac0-e6fd-d602-55f3a12e9751@apache.org
Approved	robomod@news.nic.it
Lines	17
Organization	linux.* mail to news gateway
Sender	robomod@news.nic.it
X-Original-Date	Fri, 29 Nov 2024 11:42:00 +0100
X-Original-Message-ID	<38d246ff-fac0-e6fd-d602-55f3a12e9751@apache.org>
X-Original-References	<78a8c1b6-c034-7e27-a0fa-9558adfcdfa9@free.fr> <1f8b8ba84612d8e1025cd32ef04c229936fdd117.camel@debian.org>
Xref	csiph.com linux.debian.maint.java:12837

Show key headers only | View raw

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

Back to linux.debian.maint.java | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

Re: gradle reboot Julien Plissonneau Duquène <sre4ever@free.fr> - 2024-11-16 13:50 +0100
  Re: gradle reboot Markus Koschany <apo@debian.org> - 2024-11-26 14:20 +0100
    Re: gradle reboot sre4ever@free.fr - 2024-11-27 09:20 +0100
      Re: gradle reboot Emmanuel Bourg <ebourg@apache.org> - 2024-11-29 12:00 +0100
        Re: gradle reboot sre4ever@free.fr - 2024-11-29 13:00 +0100
      Re: gradle reboot Markus Koschany <apo@debian.org> - 2024-11-30 09:50 +0100
        Re: gradle reboot sre4ever@free.fr - 2024-11-30 11:10 +0100
    Re: gradle reboot Emmanuel Bourg <ebourg@apache.org> - 2024-11-29 11:50 +0100
      Re: gradle reboot sre4ever@free.fr - 2024-11-29 12:50 +0100
        Re: gradle reboot Emmanuel Bourg <ebourg@apache.org> - 2024-11-29 13:00 +0100
          Re: gradle reboot sre4ever@free.fr - 2024-11-29 13:10 +0100
        Re: gradle reboot Toni Mueller <toni@debian.org> - 2024-11-29 13:00 +0100

csiph-web