[
https://issues.jboss.org/browse/JBIDE-19463?page=com.atlassian.jira.plugi...
]
Rob Stryker resolved JBIDE-19463.
---------------------------------
Resolution: Done
I've gone with the following text:
if( requiresRuntime ) {
requiresText = "\nThe selected profile requires a runtime.";
} else {
requiresText = "The selected profile does not require a runtime, though some
features (ex: JMX) may not be available without one.";
}
And yes, generally we like to encourage users to have a runtime where possible. Pushed
to respin-a and master
Cannot connect to remote server without runtime in JMX Navigator
----------------------------------------------------------------
Key: JBIDE-19463
URL:
https://issues.jboss.org/browse/JBIDE-19463
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jmx
Affects Versions: 4.2.3.CR1, 4.3.0.Alpha1
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 4.3.0.Beta2
Attachments: jmx-text.png
When you start a remote EAP 6.3 server with management enabled and set up and then want
to connect in JMX Navigator, it does not work - double clicking the connection will not do
anything and when you right-click, there is no Connect item.
For local servers this works fine - there is a Connect item when you right-click the
server in JMX Navigator.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)