db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Lars Heill <Lars.He...@Sun.COM>
Subject Re: Snapshot build problem on trunk
Date Thu, 18 May 2006 10:26:59 GMT

Andrew McIntyre wrote, On 05/17/06 01:37:
> 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:
>>     /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?

Thanks!  Back in business :)

I do this exercise for a "release test" scenario: what would the
quality be if the current head of trunk was final release code.
As such, I have no need for the debug bits. 
But hey, the extra 2 minutes is acceptable... ;)


View raw message