Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <1966323163.1229646464327.JavaMail.jira@brutus>
Date: Thu, 18 Dec 2008 16:27:44 -0800 (PST)
From: "Myrna van Lunteren (JIRA)" <jira@apache.org>
To: derby-dev@db.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
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:comment-tabpanel&focusedCommentId=12657947#action_12657947 ] 

Myrna van Lunteren commented on DERBY-3988:
-------------------------------------------

I believe that at one time, I found it necessary to set these properties or the PropertySetter didn't correctly find my ibm jdks. I seem to remember it assumed some default names for the installations.
However, I did some more experimenting just now, (still with my tree environment at the 727106 revision level) including having a sun jdk compiler and getting ibm jdks, and it all seems fine.
So, I don't know anymore what made me decide to need the *compile.classpath variables...


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