The project is not dead - we just have limited resources currently for adding new features.
So feel free to help out in an area that interest you
The most obvious thing would be to help out with some documentation once I figure things out enough for my own purposes.
So on to my questions to at least get the thing working.
I have the profiler running and am able to take snapshots, but have been unable to get my classes to show up in the profile.
Here are the first few lines of my jboss-profiler.properties:
Edit: And I just noticed I have the same package specified twice, going to check that.
I'm unclear as to the purpose of the private/public visibility attribute so I guessed.
I also tried the following command in an attempt to get the profiler to see my classes:
java -jar jboss-profiler-client.jar -h 0.0.0.0 -p 5400 add com.upstream.inbound.*
But no luck.
My attempts so far have been with 2.0.0.Beta5.
Start with the static configuration in order to get a setup that works for you.
The "includes" property in your case means that all public methods in com.upstream.inbound and sub-packages will be profiled.
The "visibility" property means that by default private methods are being profiled.
See Chapter 4 in the user guide for a description of the various properties - then Chapter 5 for the supported commands.
Once you got it running feel free to submit a "Quick Start" chapter as a patch to our JIRA installation.
So if I'm understanding what you are saying, it seems things should be in order. I've been through the entire document a couple of times, what it doesn't really tell me is how to exactly string all those dandy properties and commands together in a meaningful way. Obviously the default properties file goes a long way in that regard.
A couple follow-ups.
The classes in question live in an EAR, should that matter?
When I run a list from the client I get the following:
[admin@g2a jboss-profiler-2.0.0.Beta5]$ java -jar jboss-profiler-client.jar -h 0.0.0.0 -p 5400 list
Neither of those packages are defined in my config and there is no sign of the packages I did define.
Are you sure that the necessary arguments (Chapter 3.1) points to the correct file ?
Bah, that was it, I had a typo.
Thanks, you've been very helpful.