[
https://issues.jboss.org/browse/JBIDE-8626?page=com.atlassian.jira.plugin...
]
Martin Malina commented on JBIDE-8626:
--------------------------------------
Hi Snjezana,
I found out that actually the scenario is a bit different, but I think it's still a
bug.
Try this:
1. Add a search path with JBoss EAP. It will find the instance and add JBoss runtime and
Seam runtime.
2. Now remove both runtimes and remove the path.
3. Add the removed search path again. It will find the instance of JBoss EAP, but will
assume it is already added, so it will say "No runtime found".
If you close and reopen the preferences window between 2. and 3., the problem disappears.
Do you see the issue now?
Cannot click OK after searching for runtimes
--------------------------------------------
Key: JBIDE-8626
URL:
https://issues.jboss.org/browse/JBIDE-8626
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: runtimes
Affects Versions: 3.2.0.Final
Environment: RHEL 6 x86_64
OpenJDK 1.6
Reporter: Martin Malina
Assignee: Snjezana Peco
Attachments: searching-for-runtimes.jpg
I stumbled upon this problem while testing JBDS 4 on RHEL6, but I don't think it will
behave differently on RHEL5 or possibly any other platform. In fact, I just confirmed that
the same happens on Mac.
In JBoss Tools preferences, when you add a new path for runtime detection for the first
time, it find everything, but the button OK is not clickable. If you check and uncheck the
checkbox next to the found runtime, then you can click OK with no problem.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira