db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (DERBY-4619) PropertySetter fails due to an empty jre/lib directory
Date Thu, 22 Apr 2010 16:53:49 GMT

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

Kristian Waagan resolved DERBY-4619.
------------------------------------

    Issue & fix info:   (was: [Patch Available])
       Fix Version/s: 10.6.0.0
          Resolution: Fixed

Committed patch 1a to trunk with revision 936954.

I don't expect more work on this issue.

> 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
>             Fix For: 10.6.0.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.


Mime
View raw message