[ https://issues.jboss.org/browse/JBIDE-19463?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-19463: ------------------------------------- Connecting to local (or remote) jmx loads jars from the LOCAL runtime installation into a ClassLoader for the purposes of executing the remote jmx commands. This differs from our management plugins, which bundle all deps (remoting, dmr, threads, etc) for each breaking version in the server. The request here is to connect to a remote server for JMX while NOT having a local jboss-as / wildfly from which to pull JMX classes / jars. This would require bundling more libs (jboss-client-all.jar) for each different app server. This will balloon the size of our deps, and probably require new plugins. (We currently have a management.71 and management.80... now imagine adding new plugins for jmx for every app server version in the past, which requires jboss-client-all.jar for each breaking version). -- This message was sent by Atlassian JIRA (v6.3.15#6346)