Releasing 1.2.0

git-svn-id: https://pmd.svn.sourceforge.net/svnroot/pmd/trunk@2338 51baf565-9d33-0410-a72c-fc3788e3496d

pmd-eclipse/CHANGELOG.txt

@@ -1,6 +1,25 @@
 Change log for the PMD Eclipse plugin
 -------------------------------------
 
+v1.2.0 - 27/10/2003
+
+Runtime
+-------
+. Refactoring some classes to avoid the warnings about accessing private members from inner types.
+. Adding the review feature (RFE#785023 and RFE#787086)
+. Adding a Java 1.3 compatibility property for projects
+. Upgrading to PMD 1.3.0
+. Fixing encoding in rulesets (bug #810858)
+. Fixing encoding of AST (bug #819520)
+
+Development
+-----------
+. Rebuild the build.xml file according to the "Create Ant Build File" feature
+
+
+
+
+----------------------------------------------------------------------------------------
 v1.1.2 - 11/08/2003
 
 Runtime

pmd-eclipse/RELNOTES.txt

@@ -1,6 +1,38 @@
 Release notes for the PMD Eclipse Plugin
 ----------------------------------------
 
+v1.2.0 - 27/10/2003
+
+NEW : Adding a JDK 1.3 compatibility option
+-------------------------------------------
+With the upgrade to PMD 1.3, the plug-in now provide an option to flag the project to
+be JDK1.3 compatible. If the flag is checked, the "assert" keyword will be processed by
+PMD like a identifier. If the flag is unchecked, the "assert" will be processed as a
+keyword.
+
+NEW : Adding a review feature
+-----------------------------
+Some rules occured and nothing can be done to correct it (unused parameter in a
+framework abstract method or interface method, complexity warning, deep ifs,...)
+You cannot remove the rules from the configuration because other or future occurrences
+are still needed. But if the rule is still used, then the violations view will be
+polluted by the undesired violations.
+
+To address this problem, the plug-in now provide a review feature. When a violation
+occurs, if it cannot be corrected, then it can be marked as "reviewed". Reviews are
+comments placed above the targeted line of code that avoid the violation to be raised
+in future checks. As it is in the code, it is automatically shared with other developpers.
+
+To learn more about this feature, please read the online documentation in the howto
+chapter.
+
+FIX : Encoding of generated XML files
+-------------------------------------
+The plugin may generates 2 kind of XML files : rulesets file and AST files. Encoding
+problems that were sometimes encountered are now fixed.
+
+
+----------------------------------------------------------------------------------------
 v1.1.0 - 30/07/2003
 
 NEW : Redesigning the plugin configuration

pmd-eclipse/TODO.txt

@@ -1,9 +1,16 @@
-Plan for v1.2.0
+Plans
+-----
 done - implementing Review feature (RFE#787086)
-- writing doc for Review feature
+done - writing doc for Review feature
+done - fixing bug #810858 : Ruleset incorrectly written to XML: wrong encoding
+done - fixing bug #819520 : AST syntax tree does not use " in attributes
+- fixing bug #819518 : AST writes out method return types incorrectly
+- fixing bug #820241 : VariableDeclaration doesn't show variable modifiers
+- implementing lazy check feature (do not run PMD when enabling for a project ; wait still next change)
+- writing doc for lazy check feature
 - implementing working set feature
 - writing doc for working set feature
+- refactoring the JDK1.3 compatibility feature to use the project preferences
+- updating doc about JDK1.3 feature
 - improving CPD support (develop a cpd view for cpd reports)
 - updating doc for CPD support
-- implementing lazy check feature
-- writing doc for lazy check feature