db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4694) Build breaks on Mac OS X due to JDK classpath issues
Date Mon, 12 Jul 2010 10:26:49 GMT

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

Kristian Waagan commented on DERBY-4694:
----------------------------------------

I'm aware of that, the point was that the script won't try to "correct" the user if invalid
values for the various JDK versions are specified. If a user on a fresh OS X install specifies
the lib directories in ant.properties/local.properties, doing the intuitive thing will cause
Derby to fail due to the symlinking.
If no JDK paths are specified in the property files, the script should understand what Apple
has chosen to do (effectively only using JDK 1.6).

Brett, can you confirm the the script works in your environment as well?
And, out of curiosity, does your JDK installation have a 'Headers' directory?


Thanks,

> Build breaks on Mac 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
>         Environment: Mac OS X JDK 1.6
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>             Fix For: 10.7.0.0
>
>         Attachments: 1.6.0allfiles.txt, 1.6.0dirStructure.txt, antPrintCompilerPropertiesVerbose.txt,
antwithlibset.txt, antwithpatch_diff.txt, derby-4694-1a.diff, derby-4694-2a-debugging.diff,
derby-4694-2b-debugging_and_mac_fix.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.


Mime
View raw message