JProfiler as an eclipse 3.x plugin

## JProfiler as an eclipse 3.x plugin |
previous | up | next

| When JProfiler is integrated into the eclipse 3.x IDE JProfiler can be invoked from within the IDE without any further need for session configuration. Requirements: The eclipse 3.x plugin works with eclipse 3.0 and eclipse 3.1. For eclipse 2.x, a different plugin is available.

| The installation of the eclipse plugin is started by selecting "eclipse 3.x" on the IDE integration tab of JProfiler's setup wizard miscellaneous options tab of JProfiler's general settings (use Session->IDE integrations in JProfiler's main menu as a shortcut). and clicking on [Integrate] Reminder: Please close eclipse while performing the plugin installation. If you are performing the installation from JProfiler's setup wizard, please complete the entire setup first before starting eclipse. A file selector will then prompt you to locate the installation directory of eclipse. After acknowledging the completion message, you can start eclipse and check whether the installation was successful. If the menu item Run->Profile ... does not exist in the Java perspective, please enable the JProfiler plugin for this perspective under Window->Customize perspective by bringing the Command tab to front and selecting the "Profile" checkbox. eclipse provides shared infrastructure for profiling plugins that allows only one active profiler at a time. If another profiler has registered itself in eclipse, JProfiler will show a collision message dialog at startup. Please go to the `plugin` directory in your eclipse installation and delete the plugins that are specified in the warning message in order to guarantee that JProfiler will be used when you click on one of the profiling actions. If you are upgrading the integration from JProfiler <=3.2, please delete your Eclipse "configuration" directory except the config.ini file before restarting Eclipse. This is to avoid a common Eclipse 3.x plugin cache bug.

| To profile your application from eclipse, choose one of the profiling commands in the Run menu or click on the corresponding toolbar button. The profile commands are equivalent to the debug and run commands in eclipse and are part of eclipse's infrastructure. Main eclipse toolbar with "Profile" button eclipse "Run" menu with "Profile" actions The profiled application is then started just as with the usual "Run" commands. If no instance of JProfiler is currently running, JProfiler is also started, otherwise the running instance of JProfiler will be used for presenting profiling data. Every time a run configuration is profiled, a dialog box is brought up that asks you whether a new window should be opened in JProfiler. To get rid of this dialog, you can select the "Don't ask me again" checkbox. The window policy can subsequently be configured in the JProfiler settings in eclipse (see below). All profiling settings and view settings changes are persistent across session restarts. When JProfiler is used with the eclipse integration, the "Show source" action for a class or a method in one of JProfiler's view will show the source element in eclipse and not in JProfiler's integrated source code viewer.

| Several JProfiler-related settings can be adjusted in eclipse under Window->Preferences->JProfiler: The used JProfiler installation can be changed by repeating the integration from JProfiler or by adjusting the JProfiler executable in the corresponding text field. When you upgrade to a newer version of JProfiler, make sure to repeat the integration, since the plugin has to be updated, too. The window policy can be configured as Ask each time Every time you profile a run configuration, a dialog box will ask you whether a new window should be opened in JProfiler. This is the default setting. Always new window Every time you profile a run configuration, a new window will be opened in JProfiler. Reuse last window Every time you profile a run configuration, the last window will be reused in JProfiler. You can manually repeat the collision detection that is performed at startup. With the corresponding checkbox, you can also switch off collision detection at startup.