Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org Received: (qmail 83816 invoked from network); 15 Feb 2006 22:33:05 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 15 Feb 2006 22:33:05 -0000 Received: (qmail 46001 invoked by uid 500); 15 Feb 2006 22:33:02 -0000 Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org Received: (qmail 45975 invoked by uid 500); 15 Feb 2006 22:33:02 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 45964 invoked by uid 99); 15 Feb 2006 22:33:02 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Feb 2006 14:33:02 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [203.16.214.203] (HELO smtp3.adl2.internode.on.net) (203.16.214.203) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Feb 2006 14:33:01 -0800 Received: from [192.168.1.2] (ppp115-156.static.internode.on.net [150.101.115.156]) by smtp3.adl2.internode.on.net (8.13.5/8.13.5) with ESMTP id k1FMWbv4069378 for ; Thu, 16 Feb 2006 09:02:38 +1030 (CST) (envelope-from sjr@jdns.org) From: James Ring To: "Jakarta Commons Developers List" Subject: Re: [cli] Moving forward Date: Thu, 16 Feb 2006 09:32:32 +1100 User-Agent: KMail/1.9.1 References: <31cc37360602122124s1a50da8di8b084ace48074cdd@mail.gmail.com> <31cc37360602130629n6f170d59g5a5854088a8719f0@mail.gmail.com> <43F0FBDE.4080000@btopenworld.com> In-Reply-To: <43F0FBDE.4080000@btopenworld.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart27148816.Vk9nn3Ufgi"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200602160932.36329.sjr@jdns.org> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N --nextPart27148816.Vk9nn3Ufgi Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi Stephen and all, (Sorry for the late reply) On Tuesday 14 February 2006 08:36, Stephen Colebourne wrote: > Henri Yandell wrote: > > On the compatibility interface; I'd rather just drop it and spend that > > effort on migration documentation. Does raise the question of whether > > the cli2 package name ever becomes cli. Having it as cli2 does avoid > > any surprises; things flat out won't work. > > Or [commons-commandline], a completely 'new' commons project. I think that we have a better chance of getting newer versions of CLI out t= o=20 developers if we keep it within the current project. Take the Debian libcommons-cli-java package: Debian will much more readily= =20 accept new upstream releases of the same package than they will the same=20 project under a new name (I think). > Stephen Regards, James =2D-=20 James Ring --nextPart27148816.Vk9nn3Ufgi Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQBD86wE8iUSK0BWyO4RAoa3AKCO2kExy6jDFfXmdYu3FZT5OPnGuACgl58Y v1R58GqCfNl546P/ZphfR+4= =d1cu -----END PGP SIGNATURE----- --nextPart27148816.Vk9nn3Ufgi--