db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kathey Marsden <kmarsdende...@sbcglobal.net>
Subject Re: 10.3 build environment problem
Date Thu, 20 Mar 2008 16:25:56 GMT
Bryan Pendleton wrote:
> Hi all,
>
> I haven't built my 10.3 path in a few months. I thought I
> would look at merging the DERBY-2351 and DERBY-3373 patches
> back to the 10.3 branch, but when I went to build it I got:
>
> /home2/bpendleton/src/derby/10_3/10.3/java/testing/build.xml:62: The 
> following error occurred while executing this line:
> /home2/bpendleton/src/derby/10_3/10.3/java/testing/org/apache/derbyTesting/functionTests/util/build.xml:104:

> Error running ${jdk16}/bin/javac compiler
>
> I imagine that something changed in the 10.3 build and I
> didn't properly update my environment.
>
Bryan I think this is my fault.  I added the thread dump for 
stress.multi to 10.3 but used jdk16 because we don't have 
${java15compile.classpath} on 10.3 and I thought to build on 10.3 you
 had to have jdk16 set.  I see now that it is set up so that JDBC4 
classes just don't build if you don't have jdk16 set.  You can work 
around the problem by setting
jdk16=<path/to/jdk>  in your ant.properties, but I wonder  which of the 
following options I should pursue:

1) Back out the change on 10.3
2) Require jdk16 be set on 10.3 and keep the change.
3) Make the build dependent on whether jdk16 is set and only print 
thread dumps if the class is found.

I appreciate any advice.

Kathey



Mime
View raw message