Community
Participate
Working Groups
F3, likely post-2.0 This probably only happens on hpux because hpux currently does not auto-detect the vm that was used to launch Eclipse. Steps: - create a Hello World project - when it opens to its Welcome page click its Run-time Workbench link - get Problem dialog: Cannot locate JRE definition: "null". Launch aborted. A problem dialog shouldn't show "null" in its message. A message directing the user to add a vm to the Java-Installed JREs page would be more helpful.
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.
