[
https://issues.jboss.org/browse/JBIDE-17103?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-17103:
-------------------------------------
I've just investigated this for a bit.
The solution I have in my mind requires changes to an API interface:
IRuntimeDetectorDelegate
The problem with this method is twofold:
1) It enforces a workflow where we have each detector initialize a group of definitions,
so we have no feedback to know how many were created
2) The existing method initializeRuntimes(List<RuntimeDefinition>
runtimeDefinitions); is a void return with no exceptions at all.
An API change would be required to commit this. I'll make a PR just in case, but no
promises on it being accepted.
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.2.x
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)