Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <1018363154.1229438804674.JavaMail.jira@brutus>
Date: Tue, 16 Dec 2008 06:46:44 -0800 (PST)
From: "Rick Hillegas (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-3988) Set the Java 6 complilation path based
 on the Java 5 compilation path so that the JDBC4 support is always built
In-Reply-To: <1284551849.1229109584743.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-3988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rick Hillegas updated DERBY-3988:
---------------------------------

    Attachment: derby-3988-01-ac-alwaysCompileJDBC4.diff

Attaching derby-3988-01-ac-alwaysCompileJDBC4.diff. This renames compilerLevel -> compilerLevel16 as Knut suggested.

Hi Knut,

This patch doesn't change what java16compile.classpath should be set to. I have been setting java16compile.classpath to the list of jar files in my Java 6 JDK, just as java15compile.classpath is automatically set to the list of jar files in my Java 5 JDK.

Please get me back on track if I'm not following you: I think you're wondering about what happens if someone, who compiles using Java 6, checks some logic into the JDBC4 driver which mentions a new class introduced by Java 6. Today (before applying this patch) that would not be noticed by other developers who compile using Java 5. After this patch is applied, you are right, this will break the build for people who compile using Java 5. Probably we would have to back out that patch until we decided how to handle these Java 6 references.

The only solutions which have been proposed so far are:

1) Require the Java 6 compiler rather than the Java 5 compiler

2) Check in some more Java 6 stubs

I agree that we can probably wait to solve this problem until we have a concrete situation in front of us. By then, Java 6 may be supported on all the platforms we care about and (1) may be an uncontroversial solution.

Are you planning to add references to new Java 6 classes/methods soon? If so, do you have some other proposals in mind besides (1) and (2)?

> 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.