db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (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:22:44 GMT

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

Rick Hillegas commented on DERBY-3988:
--------------------------------------

Thanks for the extra information, Myrna. It looks to me like:

BEFORE this patch:

1) In your Sun environment, the build did NOT compile the JDBC4 driver

2) In your IBM environment, the build compiled the JDBC4 driver using the IBM Java 6 compiler
and the IBM Java 6 libraries

AFTER this patch:

1) In your Sun environment, the build compiled the JDBC4 driver using the Sun Java 5 compiler
and Derby's stubs (which were compiled by the Sun Java 5 compiler)

2) In your IBM environment, the build tried to compile the JDBC4 driver using the IBM Java
5 compiler and the IBM Java 6 libraries. This is what raised the version mismatch error.

Here are some possible solutions to this problem:

A) If you are using the Java 5 environment, then the build should ignore the setting of java16compile.classpath
and force it to be the classpath composed of the jdbc4 stubs followed by the java5compile.classpath

B) If you are using the Java 5 environment and java16compile.classpath is set, then the build
should raise an error saying that it can't handle the mixed signals

I would like to solicit other opinions and sleep on this.

And you raised another issue: I seem to be going blind and I don't see the java.util.HashMap
warning. Can you post that by itself?

Thanks for running these experiments!

> 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: 10.5.0.0
>            Reporter: Rick Hillegas
>            Assignee: Rick Hillegas
>         Attachments: derby-3988-01-aa-alwaysCompileJDBC4.diff, derby-3988-01-ab-alwaysCompileJDBC4.diff,
derby-3988-01-ac-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.


Mime
View raw message