[
https://issues.jboss.org/browse/JBIDE-17311?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-17311:
-------------------------------------
A check on the jmx repo (to verify that nobody specifically is polling these mbeans) shows
that there's nobody is hard-coding these mbean names or packages.
{code}
[rob@localhost jmx]$ pwd
/home/rob/code/jbtools/github/jbosstools-server/jmx
[rob@localhost jmx]$ grep -R "com.fuse" *
Binary file plugins/org.jboss.tools.jmx.jvmmonitor.core/lib/jvmmonitor-agent.jar matches
{code}
This means it should be safe to rebuild the agent jar with different package names.
jvmmonitor agent project moved + renamed into jbt-server repo
-------------------------------------------------------------
Key: JBIDE-17311
URL:
https://issues.jboss.org/browse/JBIDE-17311
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: jmx
Affects Versions: 4.2.0.Beta2
Reporter: Rob Stryker
The file "jvmmonitor-agent.jar" is currently a built component separate from
its project. This must be somehow unified with the other jvm-monitor code in terms of
where it lives and how it gets built.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)