db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rick Hillegas <Richard.Hille...@Sun.COM>
Subject Re: Snapshot build problem on trunk
Date Wed, 17 May 2006 01:08:19 GMT
Hi Andrew,

Could there be some extra magic which 
http://wiki.apache.org/db-derby/DerbySnapshotOrRelease should document? 
When I follow the steps in (2), I get an error. Here are the steps:

  587  ant clobber
  588  ls
  589  rm -rf jars
  590  rm -rf javadoc
  591  rm -rf snapshot
  592  ls
  593  ant sane
  594  ant all
  595  ant -quiet buildjars
  596  ls jars
  597  ant -quiet clobber
  598  ls jars
  599  ls jars/sane
  600  ant -quiet insane
  601  ant -Dsane=false snapshot

and here is the failure:

BUILD FAILED
C:\cygwin\home\rh161140\derby\mainline\trunk\build.xml:1546: 
C:\cygwin\home\rh161140\derby\mainline\trunk\jars\insane not found.

Andrew McIntyre wrote:

> 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



Mime
View raw message