You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "Kristian Waagan (JIRA)" <ji...@apache.org> on 2010/04/28 14:43:37 UTC

[jira] Closed: (DERBY-4619) PropertySetter fails due to an empty jre/lib directory

     [ https://issues.apache.org/jira/browse/DERBY-4619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kristian Waagan closed DERBY-4619.
----------------------------------


> 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.1.0
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>            Priority: Minor
>             Fix For: 10.6.1.0
>
>         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.
-
You can reply to this email to add a comment to the issue online.