Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <5988551.57921277470190667.JavaMail.jira@thor>
Date: Fri, 25 Jun 2010 08:49:50 -0400 (EDT)
From: "Kristian Waagan (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-4694) Build breaks on OS X due to JDK
 classpath issues
In-Reply-To: <15193013.213681275901919510.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DERBY-4694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kristian Waagan updated DERBY-4694:
-----------------------------------

    Attachment: derby-4694-1a.diff

Attaching patch 1a.

This changes the way JDKs are located when running on OS X. Up until now the defaults were used, with the patch a search will be performed like for other operating systems.

Please take the patch for a test-drive if you develop on OS X :)
I'm interested in two cases:
 - "mature" OS X installations with JDK 1.4 and 1.5 installed
 - fresh OS X installations where JDK 1.4 and JDK 1.4 are pointing to JDK 1.6.
For *both* of these it may be good to test with JAVA_HOME pointing to 1.5 [1] and 1.6 [2]. On fresh installs this shouldn't matter, but let's test it first...

Patch ready for review.


[1] /System/Library/Frameworks/JavaVM.framework/Versions/1.5/Home
[2] /System/Library/Frameworks/JavaVM.framework/Versions/1.6/Home

> Build breaks on OS X due to JDK classpath issues
> ------------------------------------------------
>
>                 Key: DERBY-4694
>                 URL: https://issues.apache.org/jira/browse/DERBY-4694
>             Project: Derby
>          Issue Type: Bug
>          Components: Build tools
>    Affects Versions: 10.7.0.0
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>         Attachments: derby-4694-1a.diff
>
>
> The Derby build breaks on OS X, apparently trying to use JDK 1.5/1.6  compile classpath for JDK 1.4.
> A quick look indicates that PropertySetter is only using defaults when configuring the classpaths, and this fails when OS X (?) creates symlinks 1.4 -> 1.6 and 1.5 -> 1.6.
> We should  investigate whether the current JAR inspection logic works on OS X with Apple JDKs as well (it is currently used for Sun and IBM JDKs, as well as for other / unknown JDKs).
> Issue was reported on derby-dev (see http://db.markmail.org/thread/wqe73b27rknuezm7 ).
> See also this thread for a related issue that may affect OS X: http://markmail.org/thread/7w24qwmvgxfctndi

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.