From derby-dev-return-69503-apmail-db-derby-dev-archive=db.apache.org@db.apache.org Tue Jun 09 01:51:22 2009 Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 26603 invoked from network); 9 Jun 2009 01:51:22 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 9 Jun 2009 01:51:22 -0000 Received: (qmail 78479 invoked by uid 500); 9 Jun 2009 01:51:34 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 78454 invoked by uid 500); 9 Jun 2009 01:51:34 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 78446 invoked by uid 99); 9 Jun 2009 01:51:34 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Jun 2009 01:51:34 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [63.82.107.6] (HELO red.amberpoint.com) (63.82.107.6) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Jun 2009 01:51:26 +0000 Received: from [127.0.0.1] (macintosh-5.local [10.10.13.21] (may be forged)) by red.amberpoint.com (8.13.8/8.13.8) with ESMTP id n591p4Bh003299 for ; Mon, 8 Jun 2009 18:51:05 -0700 Message-ID: <4A2DC008.1060002@amberpoint.com> Date: Mon, 08 Jun 2009 18:51:04 -0700 From: Bryan Pendleton User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: derby-dev@db.apache.org Subject: Re: Help with build issue References: <698569.30763.qm@web65715.mail.ac4.yahoo.com> <475551.44769.qm@web65701.mail.ac4.yahoo.com> <4A2DB559.70606@sbcglobal.net> In-Reply-To: <4A2DB559.70606@sbcglobal.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org > I have seen this before after recent message changes. I am guessing > that perhaps the tool checks the values in the jars in your classpath > instead of the build tree, but haven't verified this, because usually > when I rebuild the issue goes away. Try the following from your source > root: > > svn update > rm -rf jars/* > ant all Yes, I had the same problem too, about a month ago. As an alternate to the 'rm -rf' command, you can do ant clobber cleanjars cleandocs junit-clean Which does a very thorough clean of your svn client. thanks, bryan