Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <23897000.24831276001111241.JavaMail.jira@thor>
Date: Tue, 8 Jun 2010 08:45:11 -0400 (EDT)
From: "Kristian Waagan (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [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
In-Reply-To: <437278181.1229113904274.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Kristian Waagan commented on DERBY-3989:
----------------------------------------

Doing some investigative work on a Mac, I'm hitting this issue again. I'm also able to trigger the issue using Sun JDKs.
I believe the problem is easy to fix once we have determined that we actually do want to support this configuration:
 - invoke ant with a 1.5 JDK
 - a 1.6 JDK is available on the system (and automatically detected), but not used for compilation

We do get a version mismatch (class version 50 instead of 49) if we include the 1.6 libraries on the compile classpath used by the 1.5 compiler.
The way I see it, we have two options;
 a) Allow this configuration, JDBC 4 will be built using the JDBC 4 stubs.
 b) Disallow this configuration, abort build notifying the user that he/she should switch to a 1.6 compiler.


> 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.1.1
>            Reporter: Rick Hillegas
>             Fix For: 10.5.1.1
>
>         Attachments: derby-3989-01-aa-optionalJava5.diff, derby-3989-01-ab-optionalJava5.diff, derby-3989-01-ac-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.