Eclipse versions 3.2 and 3.3 are supported. Support for version 3.2 is provided only to allow a smoother migration to version 3.3. Future YourKit Java Profiler versions will support Eclipse 3.3 and newer only.
Plugin installation
To enable integration, you should install the profiler plugin.
To install the plugin, run the profiler.
When you run the profiler for the first time or after updating to a newer profiler version,
you will be automatically prompted to install the plugin. Also, you can explicitly launch the plugin installation wizard
via Tools | Integrate with IDE....
Eclipse 3.2 only: You may need to enable action group "Profile" in Eclipse under
Window | Customize Perspective | Commands.
If the "Profile" actions are still disabled after this,
please clean up Eclipse plugin cache, restarting Eclipse with -clean in the command line.
Profiling from Eclipse
After the plugin is installed, Profile actions appear in the toolbar ...
... in the main menu ...
... and in context menus.
You can profile J2SE and J2EE applications and applets.
Additional launch parameters can be configured in the "Run | Profile...", "YourKit Java Profiler" tab.
The "Profile" action starts the profiled application, and connects to it in profiler UI (unless opposite behavior is configured). The output of the profiled application appears in console, same as for "Run" action.
Navigation action
When profiling applications, you usually need to browse the related source code to understand the performance problems at hands. After the problem is located, you edit the source code to fix it.
Instead of forcing you to tell profiler where the source code of your application is located
and showing the code in feature-restricted custom-made "editor surrogate", YourKit provides an alternative approach.
When you have a method, class or field selected in the profiler UI,
just invoke Tools | Open Declaration in IDE Editor (F7),
to automatically open the underlying source code in the editor of your IDE - the best place to browse and edit code.
The navigation action works on the current selection and is available in both CPU and memory views. Take note of the extremely useful ability to locate the code of anonymous classes and their methods, which is a very difficult thing to do manually.
