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 Thu, 18 Dec 2008 19:51:44 GMT

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

Myrna van Lunteren commented on DERBY-3988:

Another experiment showed that with my tree sync-ed up to revision 727106, if I remove the
java16compile.classpath from the $HOME/ant.properties, the build succeeds with ibm jvm also.
The stubs/jdbc4 directory is then prepended.

Re building Driver40 with my sun setup; I maybe should have mentioned that when I build with
the sun jvms, there is no need for the java*compile.classpath settings...

As another experiment, I set up my sun jdk settings in $HOME/ant.properties, but added a java16compile.classpath
setting, and all was still fine.
So, I suspect there is a bug in the ibm jvm where it picks the wrong libraries (1.6) if both
1.5 and 1.6 are available; maybe the difference I attributed to ant version difference then
is a difference in the windows jvm.

Anyway, I have a workaround to 'cope' with this quirky behavior and the changes as per 727106;
remove the java16compile.classpath setting.
The build then uses the stubs (which I assume must get built with 1.6?) and 1.5 for everything
else...(?) I hope I understand this correctly.

It's a little frustrating that I'll have to use a different ant.properties for the different
branches but I can live with that....

> 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