Summary: | Run-time Workbench link shows bad problem dialog | ||
---|---|---|---|
Product: | [Eclipse Project] PDE | Reporter: | Grant Gayed <grant_gayed> |
Component: | UI | Assignee: | Dejan Glozic <dejan> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | Keywords: | usability |
Version: | 2.0 | ||
Target Milestone: | 2.0 F4 | ||
Hardware: | PC | ||
OS: | HP-UX | ||
Whiteboard: |
Description
Grant Gayed
2002-06-13 12:37:28 EDT
A small problem in the code - we should check if the JRE name is null and use an alternative message if it is. Both cases are valid: 1) When the JRE name is not null but cannot be found (when JRE that was initially used was removed) 2) When no JRE has been detected. We should report case 2) using a different message. Consider for F4. F4 candidate analysis: Value: Replacing confusing error message with 'null' with a more meaningful one Risk: Low - all it takes is to check if the VM name is null and use a different message string Fixed by showing a slightly different message when no JRE is found: No JRE found to launch the run-time workbench. Launch aborted. This is in contrast to the message when a JRE was used to launch the workbench before but cannot be located now: Cannot locate JRE definition: "{0}". Launch aborted. |