Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <17293581.32011271593945774.JavaMail.jira@thor>
Date: Sun, 18 Apr 2010 08:32:25 -0400 (EDT)
From: "Kristian Waagan (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-4619) PropertySetter fails due to an empty
 jre/lib directory
In-Reply-To: <15578502.31971271593465066.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Kristian Waagan updated DERBY-4619:
-----------------------------------

    Issue & fix info: [Patch Available]

> 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