Return-Path: Delivered-To: apmail-excalibur-dev-archive@www.apache.org Received: (qmail 62757 invoked from network); 19 Jun 2004 12:55:20 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 19 Jun 2004 12:55:20 -0000 Received: (qmail 6958 invoked by uid 500); 19 Jun 2004 12:55:21 -0000 Delivered-To: apmail-excalibur-dev-archive@excalibur.apache.org Received: (qmail 6902 invoked by uid 500); 19 Jun 2004 12:55:21 -0000 Mailing-List: contact dev-help@excalibur.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: List-Id: "Excalibur Developers List" Reply-To: "Excalibur Developers List" Delivered-To: mailing list dev@excalibur.apache.org Received: (qmail 6881 invoked by uid 99); 19 Jun 2004 12:55:20 -0000 Received: from [130.89.1.88] (HELO netlx014.civ.utwente.nl) (130.89.1.88) by apache.org (qpsmtpd/0.27.1) with ESMTP; Sat, 19 Jun 2004 05:55:20 -0700 Received: from [130.89.169.128] (giraffe.student.utwente.nl [130.89.169.128]) by netlx014.civ.utwente.nl (8.11.7/HKD) with ESMTP id i5JCt2N13183 for ; Sat, 19 Jun 2004 14:55:02 +0200 Message-ID: <40D437A6.30303@jicarilla.org> Date: Sat, 19 Jun 2004 14:55:02 +0200 From: Leo Simons User-Agent: Mozilla Thunderbird 0.6 (X11/20040519) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Excalibur Developers List Subject: Re: Nuke Compatibility References: <40D413CF.5000906@realityforge.org> In-Reply-To: <40D413CF.5000906@realityforge.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-UTwente-MailScanner-Information: Scanned by MailScanner. Contact helpdesk@ITBE.utwente.nl for more information. X-UTwente-MailScanner: Found to be clean X-MailScanner-From: lsimons@jicarilla.org X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Peter Donald wrote: > No one has really responded to my suggestions on where to start so I > will put them in more concrete terms. I think we should start by nuking > compatibility library. [lsimons@giraffe excalibur]$ find . -name 'project.xml' -maxdepth 3 ! -path '*compatibility*' | xargs grep -H 'excalibur-compatibility' ./trunk/monitor/project.xml: excalibur-compatibility I think that's an error (was looking into that the other day but got sidetracked), but lets be sure. > This would entail > * Bundling up the current codebase and placing it in public location > * Adding some wordage to the excalibur site describing move > * Pointing users at replacement codebases > - commons-cli for cli > - commons-collections for collections > - spice-jndikit for naming > - doug leas concurrent for concurrent > - spice-salt for io > * removing compatibility from build system > * removing compatiblity from subversion > > Does anyone have a problem with this? +1 to the nuking...but I don't like the first bullet nor the last two. Why not just a svn copy -m "excalibur-compatibility is put in graveyard mode..." \ https://svn.apache.org/repos/asf/excalibur/trunk/compatibility \ https://svn.apache.org/repos/asf/excalibur/tags/Excalibur-Compatibility-Archived svn delete -m "excalibur-compatibility is put in graveyard mode..." \ https://svn.apache.org/repos/asf/excalibur/trunk/compatibility with subversion, we don't have to go through a lot of trouble to keep the filesystem clean -- we have a DB now! - LSD --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@excalibur.apache.org For additional commands, e-mail: dev-help@excalibur.apache.org Apache Excalibur Project -- URL: http://excalibur.apache.org/