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

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

Kathey, I think your best option is to modify PropertySetter to remove the 
check for the Headers directory [1]. If that makes the build succeed, than I 
guess we should just remove the check for that directory.


[1] Just delete the line '                    new File(f, APPLE_HEADERS_DIR),'


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

Reply via email to