[
https://issues.jboss.org/browse/JBIDE-15189?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-15189:
-------------------------------------
In general, you have a new column in the dialog. If you click on this column, the
problems will be listed below, and if you double-click the problem, it will attempt to
resolve it for you (or ask you to help it resolve it).
At this time, my roll-your-own quickfix only allows one possible resolution per error.
This isn't a problem with the API but rather me not knowing how to properly display
multiple possible solutions to a problem. Also, since we currently only really have one
example, it's not necessary at the moment, since there's only one solution to
adding a missing JRE.
Things to test:
1) The popup dialog behaves as you'd expect. It disappears when you'd expect,
and stays visible when you'd expect. This includes clicking around, pressing escape,
using arrow keys and the enter key, etc.
2) The popup quickfix menu is resizable and appears in the exact position you'd
expect.
3) The dialog that pops up to fix the issue has descriptive instructions
Please only re-open this issue if a critical issue is found. If a small issue is found or
a small improvement is suggested, please open a new issue.
Check compatible JRE/JDK when adding server via runtime detection
-----------------------------------------------------------------
Key: JBIDE-15189
URL:
https://issues.jboss.org/browse/JBIDE-15189
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: runtime-detection
Affects Versions: 4.1.0.CR1
Reporter: Radim Hopp
Assignee: Rob Stryker
Fix For: 4.4.1.AM3
Now, people are not allowed to create runtime when no compatible java is configured in
eclipse (JBIDE-14858).
But when adding server and runtime via runtime detection, server and runtime are added
even though no compatible java is configured.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)