| Summary: | "Add JRE" dialog message isn't always updated | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Evgeniy Karyakin <anthropophagite> | ||||||
| Component: | Debug | Assignee: | JDT-Debug-Inbox <jdt-debug-inbox> | ||||||
| Status: | CLOSED INVALID | QA Contact: | |||||||
| Severity: | trivial | ||||||||
| Priority: | P3 | CC: | markus.kell.r, Michael_Rennie | ||||||
| Version: | 3.5.1 | ||||||||
| Target Milestone: | --- | ||||||||
| Hardware: | All | ||||||||
| OS: | All | ||||||||
| Whiteboard: | |||||||||
| Attachments: |
|
||||||||
|
Description
Evgeniy Karyakin
This works for me. Part 3 in the steps does nothing at all to the message as it remains asking "Enter the home directory of the JRE" until you specify a valid JRE home directory (one that contains the Java executable). Even if I set a valid directory and delete all the found libraries to get the "Libraries cannot be empty" message to show up, it goes away as soon as I add libraries back. Created attachment 154821 [details]
Message before clicking "Add external JARs..."
Created attachment 154822 [details]
Message after clicking "Add external JARs..."
Just got fresh Galileo (20090920-1017) onto Ubuntu Linux box and tried those exact steps, could reproduce this UI glitch: help message became error one. Also, pressing "Remove" button after successfully point to new JVM and have libraries list filled doesn't remove any record from that list, no matter if I select all of them or only one, but this may be another story. (In reply to comment #4) > Just got fresh Galileo (20090920-1017) onto Ubuntu Linux box and tried those > Using any of the steps you provided I do not see the error message after clicking / cancelling for adding libraries. I am using build 3.6M2 (Helios), can you try that and report if the problem occurs for you? (In reply to comment #5) > I am using build 3.6M2 (Helios) Ug. that should read "3.6M4 (Helios)". Helios milestone doesn't have this problem on Linux; Windows dude will surely follow. We were speaking about different versions of software, sorry, I'm closing this bug as invalid now. (In reply to comment #7) > I'm closing this bug as invalid now. Thanks for reporting back. |