You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Myrna van Lunteren (JIRA)" <ji...@apache.org> on 2009/01/12 16:14:07 UTC
[jira] Commented: (DERBY-3989) Set the Java 5 compilation path
based on the Java 6 compilation path if a Java 5 environment can't be found
but a Java 6 environment can be
[ https://issues.apache.org/jira/browse/DERBY-3989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662971#action_12662971 ]
Myrna van Lunteren commented on DERBY-3989:
-------------------------------------------
I did a quick test and found that I get a build error in the jdbc4stubs:
jdbc4stubs:
[mkdir] Created dir: <mypathto>\trunk\classes\stubs\jdbc4
[javac] Compiling 93 source files to <mypathto>\trunk\classes\stubs\jdbc4
[javac] <mypathto>\trunk\java\stubs\jdbc4\java\sql\Array.java:20: cannot access java.util.Map
[javac] bad class file: <mypathto>\ibm16\jre\lib\java.util.jar(java/util/Map.class)
[javac] class file has wrong version 50.0, should be 49.0
[javac] Please remove or make sure it appears in the correct subdirectory of the classpath.
[javac] import java.util.Map;
[javac] ^
[javac] 1 error
[javac] Compile failed; see the compiler error output for details.
I'll check on my settings etc. later, but wanted to report this & make sure this didn't get committed before I have a chance to look into it.
> Set the Java 5 compilation path based on the Java 6 compilation path if a Java 5 environment can't be found but a Java 6 environment can be
> -------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3989
> URL: https://issues.apache.org/jira/browse/DERBY-3989
> Project: Derby
> Issue Type: Improvement
> Components: Build tools
> Affects Versions: 10.5.0.0
> Reporter: Rick Hillegas
> Attachments: derby-3989-01-aa-optionalJava5.diff, derby-3989-01-ab-optionalJava5.diff
>
>
> This will make the build even more flexible. Probably involves the following changes:
> 1) Relaxing the requirement in PropertySetter that a Java 5 JDK must exist
> 2) Having PropertySetter look for a Java 6 JDK (and set java16compile.classpath accordingly) just as PropertySetter looks for a Java 5 JDK today
> 3) Changing the setCompilerProperties target in the master build script so that it
> a) requires that java15compile.classpath or java16compile.classpath is set (it's ok for both to be set)
> b) sets java15compile.classpath to ${jdbc3stubs}:${java16compile.classpath}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.