[
https://issues.jboss.org/browse/JBIDE-17103?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-17103:
-------------------------------------
Again, the patch as submitted should be 100% source-compatible, for both callers AND
implementers... so as long as all teams are compiling against the version they'll be
using, there shouldn't be a problem.
The only problem here would be if IS guys compile against our luna version but then run
against our Mars plugins.
But yes, it should be raised to them for awareness.
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)