Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: pass (asf.osuosl.org: domain of mcintyre.a@gmail.com designates
 66.249.92.171 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=eyGgPxPWfr9RFpKlxYf0llwaU7X4D/njTQJeABmBNZIkbuWZn41EV5JRjNQ6sE3WNhrApfl5cVG3XP6+aG7LzIJXrAdic0aLPoxJQxEKIyYwd8V2H++ksei9vMMMgIAIdYUs9jVdQ6m3DfpY6UD4wof6V9GlmztyG6GGBFALplI=
Message-ID: <54ac72d70605161637q4455d664l548815e1342e1734@mail.gmail.com>
Date: Tue, 16 May 2006 16:37:37 -0700
From: "Andrew McIntyre" <mcintyre.a@gmail.com>
To: derby-dev@db.apache.org
Subject: Re: Snapshot build problem on trunk
In-Reply-To: <44699D47.2010404@sun.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <44699D47.2010404@sun.com>

On 5/16/06, Lars Heill <Lars.Heill@sun.com> wrote:
> Hi,
>
> I run a daily clean snapshot build on derby trunk.
>
> The last couple of days ant snapshot has failed, saying:
>
>     BUILD FAILED
>     /home/pakker/derby/code/build.xml:1559: /home/pakker/derby/code/jars/=
sane not found.
>
> after successful runs of ant clobber, ant insane.
>
> Could this be related to the change in r405563?

Well, I guess I'm *not* the only person running the snapshot target. :-)

Yes, it is now necessary to run a sane build before the snapshot
target as well. See the instructions at
http://wiki.apache.org/db-derby/DerbySnapshotOrRelease

I suppose the part which zips up the debug-lib target could be broken
out and made conditional on the sane jars being available, but the
intended purpose of the snapshot target  is to assist committers in
producing snapshots to put up on the Derby website. As such, I'd like
to make sure that the debug-lib snapshots are posted whenever the
snapshots are updated on the site. Failing to complete the snapshot
target because the sane jars are not available is the right thing to
do here.

If it's being used for other purposes, then I'm sure we can find a
compromise. Perhaps a new target that just builds the non-debug
version of the snapshot?

andrew