I java/testing/org/apache/derby/build.xml we have the comment:
               <!-- Fix this to use the Java SE 5 classpath -->
               <pathelement path="${java16compile.classpath}"/>

but it uses java16compile.classpath. I found that this causes my build to fail using IBM 1.6 jdk. Is there any reason not to change it to use ${java15compile.classpath} ?

Thanks

Kathey

below is a larger excerpt:


 <!-- Compile package private tests. -->
   <target name="compile">
       <mkdir dir="${out.pptesting.dir}"/>

       <javac
           source="1.5"
           target="1.5"
           fork="yes"
           bootclasspath="${empty}"
           nowarn="on"
           debug="true"
           depend="${depend}"
           deprecation="${deprecation}"
           optimize="${optimize}"
           proceed="${proceed}"
           verbose="${verbose}"
           srcdir="${derby.testing.src.dir}"
           destdir="${out.pptesting.dir}">
           <classpath>
               <!-- Fix this to use the Java SE 5 classpath -->
               <pathelement path="${java16compile.classpath}"/>
               <pathelement path="${junit}"/>
               <pathelement path="${out.dir}"/>
           </classpath>
<!-- Can't rely on just compiling PackagePrivateTestSuite, as ant won't check the timestamp on the other Java files to determine
                if they have been changed since last compile then. -->
           <include name="org/apache/derby/**/*java"/>
       </javac>
   </target>

Reply via email to