Sure. I will do that.
Cheers,
-Rick
David W. Van Couvering wrote:
Great, Rick. Are you going to post this fix as a separate patch?
David
Rick Hillegas wrote:
What Andrew says. These failures turn up if you build Derby in a 1.4
environment but supplement your ant.properties with a pointer to a
1.6 installation. In that case, the build will use the 1.6 compiler
to build the optional jdbc 4 support and compilation will choke on
some discrepancies introduced by the SQLException rototill.
I fixed these build failures in my first patch for bug 862, but I
backed them out because they weren't germane to that bug's javadoc
focus. The fixes are still available in that first patch in the
following files:
M java\client\org\apache\derby\client\ClientPooledConnection40.java
M java\client\org\apache\derby\client\net\NetConnection40.java
M java\client\org\apache\derby\client\am\CallableStatement40.java
M java\client\org\apache\derby\client\am\PreparedStatement40.java
Regards,
-Rick
Andrew McIntyre wrote:
On Jan 28, 2006, at 11:05 AM, David W. Van Couvering wrote:
Hi, Andrew. Are you doing your build with JDK 1.6? I did my
build with 1.4. I'm not trying to pass off blame, just trying to
understand the circumstances better.
Hi David,
I guess this is the 'mixed' build? It's everything but the JDBC 4.0
classes compiled with JDK 1.4, and the JDBC 4.0 classes compiled
with JDK 1.6. It's what you get if you follow the instructions
posted previously to build the JDBC 4.0 classes as a part of the
regular build by setting the ant property ${jdk16} to the location
of a JDK 1.6 install.
If you don't set the jdk16 ant property, everything works fine. I
just thought I'd mention the problem because I hadn't seen it
raised anywhere else.
andrew
