Path: csiph.com!aioe.org!bofh.it!news.nic.it!robomod
From: Andreas Schildbach <andreas@schildbach.de>
Newsgroups: linux.debian.maint.java
Subject: Re: New gradle versions?
Date: Mon, 20 Nov 2017 23:30:01 +0100
Message-ID: <uO2JH-2Wv-1@gated-at.bofh.it>
References: <uNYwq-bd-1@gated-at.bofh.it> <uNYZr-zY-5@gated-at.bofh.it>
X-Mailbox-Line: From debian-java-request@lists.debian.org  Mon Nov 20 22:25:34 2017
Old-Return-Path: <glddj-debian-java-2@m.gmane.org>
X-Amavis-Spam-Status: No, score=-5.405 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_ADSP_ALL=0.8, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HK_RANDOM_ENVFROM=0.001, LDO_WHITELIST=-5, RDNS_NONE=0.793] autolearn=no autolearn_force=no
X-Policyd-Weight: using cached result; rate: -6.1
X-Injected-Via-Gmane: http://gmane.org/
Lines: 22
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
Content-Language: en-US
X-Mailing-List: <debian-java@lists.debian.org> archive/latest/20525
List-ID: <debian-java.lists.debian.org>
List-URL: <https://lists.debian.org/debian-java/>
List-Archive: https://lists.debian.org/msgid-search/ouvjj4$hss$1@blaine.gmane.org
Approved: robomod@news.nic.it
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
X-Original-Date: Mon, 20 Nov 2017 23:05:31 +0100
X-Original-Message-ID: <ouvjj4$hss$1@blaine.gmane.org>
X-Original-References: <32b559a1-bdcf-b59b-aa56-d03b04661bf0@schildbach.de> <bd0da2a6-c7e3-2697-ddf4-aea4ae152fb2@apache.org>
X-Original-X-Complaints-To: usenet@blaine.gmane.org
Xref: csiph.com linux.debian.maint.java:10157

On 11/20/2017 07:21 PM, Emmanuel Bourg wrote:

>> I wonder is there a specific reason Gradle is stuck at version 3.2.1 in
>> Debian? These days, many projects require version 4.1 or later (due to
>> the Android build chain having this requirement).
> 
> Gradle 3.2.1 was released just one year ago, it isn't that old. Gradle
> upgrades are usually difficult to deal with due to a mix of backward
> incompatible changes, integration issues with other Debian libraries and
> puzzling build errors. We are just a handful of volunteers watching over
> ~1000 Java packages, some help would be welcome.

Sorry, I didn't want to sound criminative. Just wanted to see if anyone
is working on it and where the blocker is. I understand the step up from
3.2.1 to 4.3.1 is huge, Gradle has been very active in the last years.
Actually I guess that's also the reason why the last packaged version
often can't be used any more. Maybe updating to 3.3, 3.4 or 3.5 first
would be an easier step?

My last take at Debian packaging is already 10 years old and rusty (I
did the first Spring Framework packages). At the very least I can do
testing.