[
https://issues.jboss.org/browse/JBIDE-22376?page=com.atlassian.jira.plugi...
]
Andre Dietisheim commented on JBIDE-22376:
------------------------------------------
[~tmader] I see OpenShiftServerUtils#isEapStyle [looking for "eap" or
"wildfly"|https://github.com/adietish/jbosstools-openshift/blob/master/plugins/org.jboss.tools.openshift.core/src/org/jboss/tools/openshift/core/server/OpenShiftServerUtils.java#L460]
in the [docker image
name|https://github.com/adietish/jbosstools-openshift/blob/master/plugins...]
or [build config
labels|https://github.com/adietish/jbosstools-openshift/blob/master/plugi...]
[~jcantrill] [~kconner] do you know of a better way to know whether we're talking to a
wildfly server on openshift?
We could also try to talk to the wildfly mgmt-service (most likely requires those ports to
be forwarded/exposed I guess)
Enable JMX when entering Debug mode
-----------------------------------
Key: JBIDE-22376
URL:
https://issues.jboss.org/browse/JBIDE-22376
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 4.1.1.Beta1
Reporter: Thomas Mäder
Assignee: Thomas Mäder
We need to update the deployment configuration when entering debug mode. It is not
entirely clear how to determine that an Openshift Pod has indeed a wildfly/EAP in it and
can be reached with remoting-jmx
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)