[jbosstools-dev] JMX profiling agent source code needs a home

[Max Rydahl Andersen]

Isnt it the other Way around.  this is jvm level agent that exposes stats via jmx for the profiler to report on?
It is outside/ontop of what jmx is. Jmx doesn't use it. It is jvm monitor that uses it on top/via jmx. 

I would say keep it and make it pretty much internal to start. Lets not make it API before we need it to be. 

/max (sent from my phone)


> On 23/05/2014, at 20.21, Paul Leacu <pleacu at redhat.com> wrote:
> 
> 
>   Hey -
>       I supposed its a function of whether we ever expect another application
>   to use this client api.  I guess we don't want to lose it (moving it to someplace
>   obscure) nor do we want to build it every time (it changes infrequently).
>   So - I'd say it makes the most sense to move it up from jvmmonitor (buried too deep)
>   and put it at the jbosstools-server/jmx/agent level.  It's a JMX agent after all
>   and could potentially be used by some other app.
> 
>    --paull
> 
> 
> 
> ----- Original Message -----
>> From: "Rob Stryker" <rstryker at redhat.com>
>> To: "jbosstools-dev jbosstools-dev" <jbosstools-dev at lists.jboss.org>
>> Sent: Friday, May 23, 2014 1:38:49 PM
>> Subject: [jbosstools-dev] JMX profiling agent source code needs a home
>> 
>> Hey all:
>> 
>> For those who are following the JMX additions that are occurring, we've
>> taken JVM Monitor into our repository for beta2, and intend to continue
>> taking pieces for beta3 that make sense.
>> 
>> With this in mind, we currently a home for a project in FuseIDE named
>> org.fusesource.ide.jvmmonitor.agent
>> 
>> This project is not a plugin, but is an Agent jar to be connected to a
>> given running virtual machine to take stats such as CPU usage, memory
>> usage, and other profiling data.
>> 
>> Since it's not a plugin, it's most similar to a client jar that we
>> simply need to build or fetch. Specifically, the new plugin
>> org.jboss.tools.jmx.jvmmonitor.core  needs to somehow fetch the built
>> jar and put it inside org.jboss.tools.jmx.jvmmonitor.core/lib,
>> 
>> I was wondering what the process should be for this. Should it have its
>> own repository, similar to the openshift client? Or should it still live
>> in the jbosstools-server/jmx repository somewhere to be built as part of
>> the tycho build?
>> 
>> Comments for this topic can either be responded here, or added to
>> https://issues.jboss.org/browse/JBIDE-17311
>> 
>> - Rob
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev