Integrations with IDEsSummary
EclipseIntegration into Eclipse is accomplished through the extensive Plugin architecture provided by Eclipse. It is written in Java, and has some nice features to it. Eclipse Integration will fill the TODO list of the project with each Rule Violation that PMD detects. These violations are marked in the code with the Task icon on the left hand side of the editor. The Eclipse integration was written with the version 2.0 of Eclipse, so I'm not certain if it will work on earlier versions. As Eclipse is not my primary IDE, we are looking for people who can make suggestions, and possibly even handle the care and feeding of the Eclipse plugin. EmacsIntegration with GNU Emacs is performed through an ELisp package, pmd.el. It supports two commands, "pmd-current-buffer" and "pmd-current-dir". The output is captured in a compilation buffer which allows the user to "jump" directly to the source code position associated with the PMD warnings. Borland JBuilderTo enable this OpenTool in JBuilder, place the PMDOpenTool.jar file AND the pmd-x.x.jar file (where x.x is the version id) into JBuilder's lib/ext directory. Once JBuilder is restart, the PMD OpenTool will be enabled. What you can do:
When running PMD, the results will be displayed in the MessageView under a tab called PMD Results. If you click on a violation message within this view, you will be taken to the line in the source code where the violation was detected. Things still to do:
JEditThe way I use the JEdit plugin is:
Note that you can select individual rules by going to Utilities->Global Options->Plugin Options->PMD. Also, you can change the plugin to prompt you for a directory to check by going to that same menu and selecting the "Ask for Directory" checkbox. MavenPlease see the Maven plugins web site for more information. GelHere's how to set up the PMD-Gel plugin:
That's pretty much it. Now you can open a Java project and click on Plugins->PMD and a configuration panel will pop up. You can pick which ruleset you want to run and you can also pick whether you want to run PMD on the current file or on every source file in your project. Note that the source code needs to be compilable before PMD can check it. IDEAThere's not a "real" - i.e., integrated into the same Java VM - plugin for IDEA, but using it as an IDEA External Tool works OK. Here's how to set it up:
That's pretty much it. Now you can right click on a source directory and select PMD, it'll run recursively on the source files, and the results should be displayed in a window and hyperlinked into the correct file and line of code. I usually right-click on the message window title bar and unselect "autohide" so the window doesn't go away every time I fix something in the code window. jDeveloperTo install the jDeveloper plugin, download the binary release and unzip it into your jdev/lib/ext directory. Then restart jDeveloper. To use it, open the Tools-&Preferences menu, click on the PMD option, and select a couple of rules to try. To run it, right click on either a Java source file or a .jpr file (i.e., a project file) and select PMD. Any rule violations should show up in a LogWindow at the bottom of the screen. |