[
https://issues.apache.org/jira/browse/DERBY-4619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan updated DERBY-4619:
-----------------------------------
Attachment: derby-4619-1a-fix_for_empty_libdir.diff
Attaching patch 1a, which casues null to be returned instead of the empty
string. This will result in the default classpath (typically stubs plus the
higher version JDK classpath) being used if the JDK isn't found, if possible.
I also added a debug method to print debug information, and added a few more
debug statements.
Patch ready for review.
> PropertySetter fails due to an empty jre/lib directory
> ------------------------------------------------------
>
> Key: DERBY-4619
> URL: https://issues.apache.org/jira/browse/DERBY-4619
> Project: Derby
> Issue Type: Bug
> Components: Build tools
> Affects Versions: 10.6.0.0
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Priority: Minor
> Attachments: derby-4619-1a-fix_for_empty_libdir.diff
>
>
> If a JDK directory with an empty jre/lib directory is chosen by the old
> algorithm for detecting JDKs on the build system, the build fails because
> the classpath is set to the empty string instead of the default (stubs and
> the higher level JDK classpath).
> The situation causing this problem can arise if a JDK with extension libs is
> uninstalled. Depending on the packaging system, this may leave the
> jre/lib/ext directory behind.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
