[
https://issues.apache.org/jira/browse/DERBY-5469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13135399#comment-13135399
]
Knut Anders Hatlen commented on DERBY-5469:
-------------------------------------------
I agree that PropertySetter is starting to get too complex. In my opinion, it
would be sufficient if PropertySetter were able to detect which Java version
Ant is running (which can be done by inspecting system properties, no need to
parse rt.jar) and set up the various compile classpaths based on that Java
instance. This would still allow easy building of Derby, which was the goal
when PropertySetter was introduced. If someone wants a more exotic setup (like
pointing java14compile.classpath to actual Java 1.4 runtime libraries), they
should be able to override the compile classpaths with properties the same way
as today, but PropertySetter doesn't need to do that automatically.
Although it might be possible to make PropertySetter detect all old Java
versions from all vendors on all platforms, and to keep it updated, I'd much
rather spend my time writing database code than maintaining PropertySetter... :)
> 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
