Apex PMD installs statistics

vscode Apex Pmd

Allows you to run Apex Static Analysis directly in vscode on Apex, VisualForce & other XML metadata files.

Features

To start the command you can click in the menu on Help/Show All Commands or press the hotkey <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> and type Apex.

Current actions Supported

• Run analysis on file open
• Run analysis on file save
• Run analysis on file change (new!)
• Run analysis on entire workspace
• Run analysis on single file
• Ability to define your own ruleset

System Requirements

• Must have JRE >= 1.8 installed and in path
• See PMD System Requirements for more details

Configuration

• rulesets (optional): set to override default ruleset (see "Defining your own ruleset" for more details)

• runOnFileOpen: run every time a file is opened in vscode

• runOnFileSave: run every time a file is saved

• runOnFileChange: Run when a file is changed. NOTE: this is "debounced" to prevent performance issues. Delay can be adjusted via onFileChangeDebounce.

• priorityErrorThreshold: Determines at what priority level 'errors' will be added. Anything less will be a warning or hint

• priorityWarnThreshold: Determines at what priority level 'warnings' will be added. Anything less will be a hint

• enableCache: Creates a cache file for PMD to run faster. Will create a .pmdCache file in your workspace

• pmdBinPath (prev. pmdPath) (optional): set to override the default pmd binaries. This should point to the PMD folder which contains folders lib and bin. Most likely it is called libexec. WARNING: Since v0.6.0, this extension no longer supports PMD 6x. If you receive an error, please clear this setting!

• additionalClassPaths (optional): set of paths to be appended to classpath. Used to find jar files containing custom rule definitions. Can be absolute or relative to workspace.

• commandBufferSize Size of buffer used to collect PMD command output (MB), may need to be increased for very large projects

• jrePath (Optional) Path to JRE (Folder that contains which contains bin/java)

• apexRootDirectory (optional, since 0.9.0): Whether and how to set PMD_APEX_ROOT_DIRECTORY env variable. This variable should point to the sfdx project directory, which contains the file sfdx-project.json.

  This is needed for the rule UnusedMethod which utilizes Apex Language Server which needs a well-formed sfdx project.

  • off = Do not set PMD_APEX_ROOT_DIRECTORY at all
  • automatic = (default) Automatically find the nearest sfdx-project.json file in a parent directory and use that directory
  • custom = Use a custom location for PMD_APEX_ROOT_DIRECTORY provided by "customValue". It should point to the directory where the sfdx-project.json file is located. This is only used, if the "mode"=="custom".

• enableDebugOutput: Logs PMD's debug messages to help troubleshooting.

Defining your own "Ruleset"

I recommend you use the default ruleset as a starting point.

Set apexPMD.rulesets string array to reference your custom rulesets. You can either use the absolute paths, or a relative paths from your workspace (EG my-apex-rules.xml).

You can also mention the default ruleset in apexPMD.rulesets. To do this add default value to the array.

Apex Ruleset Reference

NOTE: If you move away from the default ruleset in an sfdx project, make sure to exclude the .sfdx and .sf generated classes by keeping these lines:

<exclude-pattern>.*/.sfdx/.*</exclude-pattern>

<exclude-pattern>.*/.sf/.*</exclude-pattern>

Using custom rules written in Java

If you want to use your own custom rules from a jar file, then the jar file must be on the classpath. By default, the PMD folder and the workspace root folder are included in the classpath. You can add further folders using the additionalClassPaths setting. This "Hello world" example is a good starting place for beginners.

Troubleshooting

The plugin creates an own output channel "Apex PMD" in the output view. This shows the output of the PMD command that is executed in the background. In case of any problem, this output channel might contain the underlying error. When reporting an issue, please include any error messages from this output channel.

Developing/Contributing

Prerequisites

• node
• bash: npm calls shell scripts and therefore bash is needed. Under Windows, make sure to run npm from within git-bash.
• java: needs to be installed already. It is needed for executing PMD later on.

Setup & Run

1. git clone
2. npm install
3. debug -> run extension…