[
https://issues.apache.org/jira/browse/DERBY-5469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13135343#comment-13135343
]
Rick Hillegas commented on DERBY-5469:
--------------------------------------
Thanks, Kathey. The PropertySetter task does look at system properties.
However, where it's falling down is in the part of its processing where it
looks around the directory system to find other JDKs. It does this so that it
can find libraries for lower versions of the JDK. In particular, it wants to
find a 1.4 JDK if it can so that it can use those libraries when compiling the
bulk of Derby code. Being able to use those libraries means that the compiler
can object if someone tries to call a Java 6 method in code which is supposed
to run on small devices.
It's a very tricky piece of logic and I am beginning to fear that the number of
special cases may be expanding faster than we can keep up with them.
Standard attributes in the jar manifest are documented here:
http://download.oracle.com/javase/1.4.2/docs/guide/jar/jar.html#Manifest%20Specification
Thanks,
-Rick
> Make it possible to build Derby if you are on Mac OS X and your JDK is JDK 7
> ----------------------------------------------------------------------------
>
> Key: DERBY-5469
> URL: https://issues.apache.org/jira/browse/DERBY-5469
> Project: Derby
> Issue Type: Improvement
> Components: Build tools
> Reporter: Rick Hillegas
> Assignee: Rick Hillegas
> Attachments: derby-5469-01-ae-add17andJavadoc.diff,
> derby-5469-01-af-dontSetUprevVariables.diff, derby-5469-01-ag-cleanedUp.diff
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
