2003-03-27 22:08:43 +00:00
|
|
|
Release notes for the PMD Eclipse Plugin
|
2003-03-30 20:54:44 +00:00
|
|
|
----------------------------------------
|
|
|
|
|
|
|
|
|
|
v0.5.1 - release date
|
|
|
|
|
|
|
|
|
|
NEW : Adding a logging facility
|
|
|
|
|
-------------------------------
|
|
|
|
|
The logging support is based on Log4J from Apache (see: http://jakarta.apache.org/log4j).
|
|
|
|
|
The default is to log at the warn level to the file "pmd-eclipse.log" using a rolling
|
|
|
|
|
file appender of 10 MB and one backup file.
|
|
|
|
|
The file is located in the {user.dir} directory which should be your Eclipse home
|
|
|
|
|
directory
|
|
|
|
|
To change these options, simply edit the "log4j.xml" file located in the plugin. Please
|
|
|
|
|
read the Log4J doc to learn how to update this file.
|
|
|
|
|
|
|
|
|
|
NEW : PMD actions from folder and package popups
|
|
|
|
|
------------------------------------------------
|
|
|
|
|
Now, PMD actions (check code and remove markers) are available from the popup menus of
|
|
|
|
|
a folder (resource navigator view) and package (package explorer view).
|
|
|
|
|
|
|
|
|
|
UPDATED :
|
|
|
|
|
---------
|
|
|
|
|
Now, no more error message is displayed when PMD is executed against a file with syntax
|
|
|
|
|
errors.
|
|
|
|
|
|
|
|
|
|
|
2003-03-27 22:08:43 +00:00
|
|
|
|
|
|
|
|
|
2003-05-19 22:28:47 +00:00
|
|
|
----------------------------------------------------------------------------------------
|
2003-03-27 22:08:43 +00:00
|
|
|
v0.5.0 - 19/03/2003
|
|
|
|
|
|
|
|
|
|
NEW : Using PMD as a project incremental builder
|
|
|
|
|
------------------------------------------------
|
|
|
|
|
When PMD is used as an incremental builder, then violations are added as problem marker. Then,
|
|
|
|
|
markers will be removed when violations are fixed.
|
|
|
|
|
To enable PMD as a incremental, simply check "enable PMD" on your project PMD property
|
|
|
|
|
page.
|
|
|
|
|
|
|
|
|
|
UPDATED :
|
|
|
|
|
---------
|
|
|
|
|
When PMD is used "one shot" from the popup menu, then violations are added as task. Then, markers
|
|
|
|
|
should be removed manually via the popup menus, either from the project (all violations for this
|
|
|
|
|
project will be removed), or from a file or group of files (all violations for these files will be
|
|
|
|
|
removed) or from the task view (all violations for all projects will be removed).
|
|
|
|
|
|
|
|
|
|
PMD markers (violations) can be filtered in the task view : either PMD task marker or PMD problem
|
|
|
|
|
marker or both.
|
|
|
|
|
|
|
|
|
|
PMD rule violations have a priority from 1 to 5. Markers have only 3 level of severity, so the mapping is as follow :
|
|
|
|
|
PMD priority 1 -> severity error, priority high
|
|
|
|
|
PMD priority 2 -> severity error, priority normal
|
|
|
|
|
PMD priority 3 -> severity warning, priority high
|
|
|
|
|
PMD priority 4 -> severity warning, priority normal
|
|
|
|
|
PMD priority 5 -> severity information, priority normal
|
|
|
|
|
|
|
|
|
|
MISC :
|
|
|
|
|
------
|
|
|
|
|
PMD engine is not shipped with the source archive. Download it from source forge and install it in
|
|
|
|
|
a lib subdirectory.
|
|
|
|
|
|
