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/18 14:24:25 UTC
[jira] Created: (DERBY-4619) PropertySetter fails due to an empty
jre/lib directory
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
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
[jira] Closed: (DERBY-4619) PropertySetter fails due to an empty
jre/lib directory
Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Resolved: (DERBY-4619) PropertySetter fails due to an empty
jre/lib directory
Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (DERBY-4619) PropertySetter fails due to an empty
jre/lib directory
Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
[ 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
[jira] Updated: (DERBY-4619) PropertySetter fails due to an empty
jre/lib directory
Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
[ 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