Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 3D88F200D68 for ; Thu, 28 Dec 2017 11:05:12 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 3C0B5160C1F; Thu, 28 Dec 2017 10:05:12 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 7A031160C16 for ; Thu, 28 Dec 2017 11:05:11 +0100 (CET) Received: (qmail 11232 invoked by uid 500); 28 Dec 2017 10:05:10 -0000 Mailing-List: contact dev-help@ant.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list dev@ant.apache.org Received: (qmail 11221 invoked by uid 99); 28 Dec 2017 10:05:10 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Dec 2017 10:05:10 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 2A713DFC2F; Thu, 28 Dec 2017 10:05:10 +0000 (UTC) From: bodewig To: dev@ant.apache.org Reply-To: dev@ant.apache.org References: In-Reply-To: Subject: [GitHub] ant issue #54: Let’s use Ivy (properly!) and drop Maven Ant tasks, Commons... Content-Type: text/plain Message-Id: <20171228100510.2A713DFC2F@git1-us-west.apache.org> Date: Thu, 28 Dec 2017 10:05:10 +0000 (UTC) archived-at: Thu, 28 Dec 2017 10:05:12 -0000 Github user bodewig commented on the issue: https://github.com/apache/ant/pull/54 For the changes you plan to introduce to the release process I urge you to not change things just because they look better to you. As it stands I'd be your main user and I'm fine with the process as it is and am completely happy with signing artifacts manually (which happens whenever I cut a release, so twice every few months at best). Our Nexus is going to create extraneous checksums anyway, no matter what Ivy does. Not sure about your second point (I don't declare anything anywhere). You are completely losing me when you talk about the svn resolver, I don't see any reason to use Ivy in order to publish artifacts to dist.apache.org at all. --- --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org For additional commands, e-mail: dev-help@ant.apache.org