[
https://issues.jboss.org/browse/JBIDE-17103?page=com.atlassian.jira.plugi...
]
Martin Malina closed JBIDE-17103.
---------------------------------
Verified in JBDS 9.0.0.Beta1 B34. I was able to get that error if I removed the server
after it was found. Also, currently you can get this error for WildFly 10 - it is found,
but not added, so this error also shows up. Personally, I would prefer more readable text
like "Unable to add runtimes." rather than "Unable to initialize some
runtime paths." - that seems a bit cryptic to me. But I guess it's just me ;)
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.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)