[ https://issues.jboss.org/browse/JBIDE-19463?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-19463: ------------------------------------- Honestly, I think it's very unlikely we'd get a usecase like this up and running in any reasonable time. The reality of it is that we'd probably need to add at least a dozen new plugins depending on how far back we wanted to extend this support, each with a copy of the jboss client-all jar. These client jars are as small as 400k (back in jboss 4.2) up to 7 meg (for wf 8.1). Even averaging this out, it could add 30 to 50 megs to the distribution easily. It would also add a huge amount of complexity, and a testing nightmare for QE to accurately verify. The reason it'd require so many plugins is because the jar being added is the client-all jar. At least some classes of the client-all jar change in almost every release, and so it'd be a huge investigative task to figure out the full set of classes that are needed for the jmx requests, whether those specific class files have changed in any micro / minor changes, whether they've changed in a breaking manner, etc etc, for all releases in the past. Splitting the jar would be an option, putting jars only with those classes needed for JMX requests, but this is pretty much rejected out-of-hand because we are not in the business of modifying or customizing app-server jars (even client jars distributed with the app server). If I had to imagine a solution, the closest I could come is to being able to add some UI so that you can set the location of a client-all jar from somewhere on your disk for your runtime-less server, and it would be up to you to ensure its the proper jar. But even that comes with its own UI perils (where to put such a UI? Server editor? How to make it hidden enough to not distract users who don't need it without also making it invisible to people looking for it?) In short, I think it's highly unlikely we'll be able to get this feature going in any meaningful fashion. [~maxandersen] Any thoughts? -- This message was sent by Atlassian JIRA (v6.3.15#6346)