Bug 126304 - JDK_TOOLS not always registered as classpath variable
JDK_TOOLS not always registered as classpath variable
Status: CLOSED ERRATA
Product: Red Hat Developer Suite
Classification: Retired
Component: Lomboz (Show other bugs)
1.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Handcock
eclipse-bugs
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2004-06-18 14:51 EDT by Jeremy Handcock
Modified: 2007-04-18 13:09 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-06-18 19:20:27 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jeremy Handcock 2004-06-18 14:51:22 EDT
Description of problem: Lomboz requires tools.jar from a JDK around,
and Lomboz projects expect the path to it to be registered as the
JDK_TOOLS classpath variable.  The path is currently only registered
when the Lomboz preferences are modified.


Version-Release number of selected component (if applicable):
eclipse-lomboz-2.1.2-6


How reproducible: Always.


Steps to Reproduce:
1. Launch eclipse with a new workspace, and don't touch the Lomboz
preferences.
2. Create a new J2EE project.
  
Actual results: JDK_TOOLS classpath variable is unbound and J2EE
projects do not build properly.

Additional info: I'll put together a patch for this that I'll pass
upstream as well.
Comment 1 Jeremy Handcock 2004-06-18 19:20:27 EDT
I just checked in a patch for this that registers the classpath
variable at plug-in initialization.  I'll send it to ObjectWeb as well.
Comment 2 Jay Turner 2004-09-02 01:32:33 EDT
An errata has been issued which should help the problem 
described in this bug report. This report is therefore being 
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, 
please follow the link below. You may reopen this bug report 
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2004-365.html

Note You need to log in before you can comment on or make changes to this bug.