]
Rob Stryker updated JBIDE-17103:
--------------------------------
Attachment: JBIDE-17103.png
Screenshot of how the error appears.
To verify this screenshot exists:
1) Go to JBoss Runtime Detection page
2) Add a path pointing to a WF installation
3) Wait for dialog indicating 1 new runtime found
4) Delete the entire folder from your HD
5) Press "OK" in the "searching for runtimes..." page
6) See error dialog appear.
No warning/error is shown when detected runtime fails to be added
-----------------------------------------------------------------
Key: JBIDE-17103
URL:
https://issues.jboss.org/browse/JBIDE-17103
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.2.0.Beta1
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 4.3.0.Beta1
Attachments: JBIDE-17103.png
When there is a new version of a runtime, e.g. WildFly 8.1, that is not yet supported by
the tooling, runtime detection usually detects it alright, but when you then click OK, the
runtime+server are not added. And there is no error anywhere at all - we should fix that.