[jbosstools-issues] [JBoss JIRA] (JBIDE-17311) jvmmonitor agent project moved + renamed into jbt-server repo

[Rob Stryker (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-17311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980968#comment-12980968 ] 

Rob Stryker commented on JBIDE-17311:
-------------------------------------

I simply meant that the agent code needs to find a home to live, and was suggesting it live near the "other" jvmmonitor code, ie, the plugins in jbosstools-server.   But I'm not sure where it should go. Openshift's client jar has its own github repository. And nobody seems to know how to build the agent jar's source code. 

Also, there's a danger that changing the package names in the agent might break parts of our jvmmonitor plugs that may look for those mbeans. I'm currently not able to quantify this risk, though. It might be non-existant, or it might be very high. At this point, I have no idea.  But changing the name of the mbeans the agent adds will break anyone looking for those mbeans. 

> 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
>             Fix For: 4.2.0.Beta3
>
>
> 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)