From e83324fe14b8f7f7f1c92931b7f380a2127e7cf2 Mon Sep 17 00:00:00 2001 From: Tom Copeland Date: Thu, 18 Jul 2002 18:20:06 +0000 Subject: [PATCH] post-release stuff git-svn-id: https://pmd.svn.sourceforge.net/svnroot/pmd/trunk@444 51baf565-9d33-0410-a72c-fc3788e3496d --- pmd/xdocs/integrations.xml | 17 ++++++++--------- pmd/xdocs/running.xml | 26 +++++++++++--------------- 2 files changed, 19 insertions(+), 24 deletions(-) diff --git a/pmd/xdocs/integrations.xml b/pmd/xdocs/integrations.xml index 15aee74361..038b9a9dc3 100644 --- a/pmd/xdocs/integrations.xml +++ b/pmd/xdocs/integrations.xml @@ -31,7 +31,7 @@ X JEdit pmd-jedit - 0.3 + 0.4 tomcopeland X Maven @@ -81,15 +81,15 @@ code which caused it.

-To enable this OpenTool in JBuilder, place the PMDOpenTool.jar file AND the pmd-x.x.jar file (where +To 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. +will be enabled. What you can do: -

  • Check a single file by bringing up the context menu from the file tab and selecting PMDCheck
  • +
  • Check a single file by bringing up the context menu from the file tab and selecting PMDCheck
  • Configure the rulesets that the PMD OpenTool will use by selecting Tools->PMD->Configure PMD
  • Check all the files in a project by brining up the context menu for the project node and selecting PMD Check Project
  • -

    When running PMD, the results will be displayed in the MessageView under a tab called PMD Results. If you click on a +

    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: @@ -102,12 +102,11 @@ violation message within this view, you will be taken to the line in the source

    This is more or less the standard JEdit plugin - open a file, select Plugins->PMD->Check code and -you get a popup list of problems. Things to do: +you get a popup list of problems. It uses the ErrorList plugin which provides the "jump to the correct line" +and syntax highlighting functionality. Things to do:

    diff --git a/pmd/xdocs/running.xml b/pmd/xdocs/running.xml index 8d5ce0e77e..a5b70ca5e2 100644 --- a/pmd/xdocs/running.xml +++ b/pmd/xdocs/running.xml @@ -10,21 +10,17 @@
    • Type run <filename> <report format>, <rule set file>i.e.:
    • - - -run c:\data\pmd\pmd\test-data\Unused1.java xml rulesets/unusedcode.xml - - -c:\data\pmd\pmd\test-data\Unused1.java -5 -Found unused local variable 'fr' - - -C:\data\pmd\pmd\etc> -]]> - - +
      +C:\data\pmd\pmd\etc>run c:\data\pmd\pmd\test-data\Unused1.java xml rulesets/unusedcode.xml +<?xml version="1.0"?><pmd> +<ruleviolation> +<file>c:\data\pmd\pmd\test-data\Unused1.java</file> +<line>5</line> +<description>Found unused local variable 'fr'</description> +</ruleviolation> +</pmd> +C:\data\pmd\pmd\etc> +
    • Notice that in this case the output is in XML, so you can redirect it to a file and XSLT it or whatever