db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "V.Narayanan (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-932) Fix the way JDK 1.6 specific files are built
Date Fri, 10 Feb 2006 10:53:56 GMT
    [ http://issues.apache.org/jira/browse/DERBY-932?page=comments#action_12365875 ] 

V.Narayanan commented on DERBY-932:

Hi David,
The jdbc4 test suite doesn't build. You have forgotten to include entry for tests/jdbc4 in
Here is the diff for the same.

Index: java/testing/build.xml
--- java/testing/build.xml      (revision 376591)
+++ java/testing/build.xml      (working copy)
@@ -56,6 +56,7 @@
     <ant dir="${derby.testing.src.dir}/${derby.testing.functest.dir}/tests/derbynet"/>
     <ant dir="${derby.testing.src.dir}/${derby.testing.functest.dir}/tests/unit"/>
     <ant dir="${derby.testing.src.dir}/${derby.testing.functest.dir}/tests/i18n"/>
+    <ant dir="${derby.testing.src.dir}/${derby.testing.functest.dir}/tests/jdbc4"/>
     <ant dir="${derby.testing.src.dir}/${derby.testing.functest.dir}/tests/largedata"/>
     <ant dir="${derby.testing.src.dir}/${derby.testing.functest.dir}/multi/stress"/>
     <ant dir="${derby.testing.src.dir}/${derby.testing.functest.dir}/master"/>

> Fix the way JDK 1.6 specific files are built
> --------------------------------------------
>          Key: DERBY-932
>          URL: http://issues.apache.org/jira/browse/DERBY-932
>      Project: Derby
>         Type: Bug
>     Reporter: David Van Couvering
>     Assignee: David Van Couvering

> Currently these files are built using the exec ant task.  This results in odd behavior,
such as the fact as the build doesn't end if there's a build failure with one of these targets.
 Also, in NetBeans the compile errors are not "clickable".  Fix this to use javac where you
specify the compiler executable path.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message