db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3988) Set the Java 6 complilation path based on the Java 5 compilation path so that the JDBC4 support is always built
Date Wed, 17 Dec 2008 00:56:44 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12657246#action_12657246

Myrna van Lunteren commented on DERBY-3988:

Re hashMap warning...You're not blind, I am...After adding the stubs/jdbc4 dir to the java16compile.classpath,
I get a new set of warnings (and I only spotted 1):
- java\engine\org\apache\derby\iapi\jdbc\BrokeredConnection40.java:33: cannot access java.util.Properties
- java\engine\org\apache\derby\impl\jdbc\EmbedConnection40.java:33: cannot access java.util.HashMap
- java\engine\org\apache\derby\jdbc\Driver40.java:48: cannot access java.util.Properties
- java\client\org\apache\derby\client\am\LogicalConnection40.java:32: cannot access java.util.Properties
- java\testing\org\apache\derbyTesting\functionTests\tests\jdbc4\BlobTest.java:146: cannot
access java.util.HashMap

And re 40 driver getting built, I can assure you it got built.
I can svn update to that state and build and send the result, but in the mean time, I've got
a non-working environment.
Can you back out your latest commit until we've figured out a solution?

> Set the Java 6 complilation path based on the Java 5 compilation path so that the JDBC4
support is always built
> ---------------------------------------------------------------------------------------------------------------
>                 Key: DERBY-3988
>                 URL: https://issues.apache.org/jira/browse/DERBY-3988
>             Project: Derby
>          Issue Type: Improvement
>          Components: Build tools
>    Affects Versions:
>            Reporter: Rick Hillegas
>            Assignee: Rick Hillegas
>         Attachments: derby-3988-01-aa-alwaysCompileJDBC4.diff, derby-3988-01-ab-alwaysCompileJDBC4.diff,
> Now that we have checked in the JDBC4 stubs, it ought to be possible to build the JDBC4
support with just the Java 5 libraries and compiler. Set java16compile.classpath=${jdbc4stubs}:${java15compile.classpath}.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message