You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by Bryan Pendleton <bp...@amberpoint.com> on 2008/03/20 17:04:09 UTC

10.3 build environment problem

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.

Or maybe I changed my environment for my 10.4/trunk builds
and somehow messed up my 10.3 environment.

Does anybody recognize the above error message, or have
a suggestion about what I might have mis-configured?

If it helps, line 104 of that build.xml is this call to javac:

     <javac
       source="1.5"
       target="1.5"
       fork="yes"
       executable="${jdk16}/bin/javac"
       bootclasspath="${empty}"
       nowarn="on"
       debug="true"
       depend="${depend}"
       deprecation="${deprecation}"
       optimize="${optimize}"
       proceed="${proceed}"
       verbose="${verbose}"
       srcdir="${derby.testing.src.dir}"
       destdir="${out.dir}">
       <classpath>
         <pathelement path="${java16compile.classpath}"/>
       </classpath>
     <include name="${this.dir}/ThreadDump.java"/>
     </javac>

thanks,

bryan


Re: 10.3 build environment problem

Posted by Bryan Pendleton <bp...@amberpoint.com>.
> 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:

Thanks Kathey! For now that workaround works for me. I don't have
any immediate plans to do a lot more work on 10.3, so I don't have
much of an opinion about the options you proposed.

thanks,

bryan



Re: 10.3 build environment problem

Posted by Rick Hillegas <Ri...@Sun.COM>.
Kathey Marsden wrote:
> 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
>
>
Hi Kathey,

I think that option (2) should be avoided. I think that the trunk would 
be the best place to introduce that kind of change and I think that 
change is still unattractive for the trunk because of the lack of Java 6 
support on some important platforms.

Regards,
-Rick

Re: 10.3 build environment problem

Posted by Kathey Marsden <km...@sbcglobal.net>.
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