| 6766 06.01.2009 21:25:29, by xlv:
ant targets cleanup:
cpd target removed
cpdOnPmd generates xml file (to be used by new Hudson cpd plugin)
cpdOnPmd report generated in "reports" target |
| 6765 31.12.2008 09:01:24, by rgustav:
Update to current PMD 5.0, fixes issued with RuleSetFactory.getRegisteredRuleSets() due to missing ecmascript ruleset.properties.
Update PreferenceManagerImpl for RuleSetFactory changes. |
| 6764 31.12.2008 08:43:18, by rgustav:
Add missing ecmascript rulesets.properties. |
| 6763 31.12.2008 01:18:19, by rgustav:
Remove ExternalRuleID and SimpleRuleSetNameMapper, and replace with RuleSetReferenceId. RuleSetFactory APIs updated to use RuleSetReferenceId, including support for RuleSet internal references.
This completes the standardization of RuleSet reference use throughout PMD. See RuleSetReferenceId for the specifics of the standard scheme. |
| 6762 29.12.2008 21:10:52, by xlv:
update PMD jar file to revision 6760 |
| 6761 29.12.2008 20:26:21, by hooperbloob:
Bugfix for property updates while in grouped rule mode, enabled multi-select in rule list - users can modify priority levels via new popup menu, bugfix for multi-value renderers, new RuleSelection class. I'm still waiting for usability/feature feedback comments!
Need to implement: scrolling panel for property values, a splitter bar between rules & property tabs below, proper editors for enum types and multi-values, especially classes & interfaces. Still need to deal with statistical value rules - they throw exceptions at the moment, those guys have no defaults for now (not necessary?)
*** Please to not update the old PMDPreferencesPage, apply any necessary changes to the class of the same name in the temporary .br package. The old one remains as is where it is for comparison with the new one that shows up in the Eclipse preference panel right below the PMD entry ("Ruleset preferences - br"). |
| 6760 24.12.2008 08:18:56, by hooperbloob:
Rules can now return whether they are using default property values or not |
| 6759 21.12.2008 16:36:56, by rpelisse:
Working on bug : https://sourceforge.net/tracker2/?func=detail&aid=2410201&group_id=56262&atid=479921
I reproduced the issue and trace the problem back to the symbol table (More exactly a method of the NameOccurences class). I also added a test to reproduced the issue here. (Also added a little javadoc).
I'm not really although how to "assert" results in this test, not really sure how the symbol table should be expected to behave here.
No more time right now for this, i'll try see through this week.
Note: I'll patch trunk when I'll have fix for good this issue. |
| 6758 20.12.2008 00:23:32, by rgustav:
Add support for 'null' or empty 'id', so that anonymous references can be created by the Test framework.
Flesh out the internal Rule reference support, by allowing it to pair with an external reference that can get an actual InputStream for use by the RuleSetFactory. |
| 6757 18.12.2008 17:01:08, by rgustav:
Update JavaDoc to include examples. |
| 6756 18.12.2008 16:55:53, by rgustav:
Create the RuleSetReferenceId class. The goal is to provide a single means of identifying a RuleSet for all mechanisms which use this (RuleSetFactory, RuleSet XML, and command line). This class merges together the functionality of ExternalRuleID and SimpleRuleSetNameMapper.
My original impetus for this change is the following additional feature... support for creating a reference to a Rule in the "current" RuleSet. This has no external use, but can/will be used to enhance the RuleSetFactory to allow references to a Rule in the current RuleSet, without having to make a fully qualified reference to the current RuleSet. It is like being able to call a static method defined in the current Java class, without having to prefix the method with the FQN of the current Java class.
I will now work on refactoring everything to use this class.
When done, this change will also make it possible to list a single Rule anywhere a RuleSet name is to be expected, be it in the RuleSet XML, or the PMD command line (a feature requested in the past). |
| 6755 14.12.2008 21:56:14, by xlv:
test case for [ 2429017 ] Failed parsing byte[].class.hashCode() |
| 6754 13.12.2008 01:13:39, by xlv:
Fixed bug - JUnitTestsShouldIncludeAssert now detects Junit 4 Assert.assert... constructs |
| 6753 13.12.2008 01:12:54, by xlv:
Fixed bug - JUnitTestsShouldIncludeAssert now detects Junit 4 Assert.assert... constructs |
| 6752 11.12.2008 19:50:48, by xlv:
deprecated JRE_LIB replaced with org.eclipse.jdt.launching.JRE_CONTAINER |
| 6751 11.12.2008 08:25:27, by xlv:
oops, NPE in previous commit... |
| 6750 11.12.2008 08:25:13, by xlv:
oops, NPE in previous commit... |
| 6749 11.12.2008 08:09:45, by xlv:
oops, NPE in previous commit... |
| 6748 11.12.2008 08:09:14, by xlv:
oops, NPE in previous commit... |
| 6747 11.12.2008 07:32:36, by xlv:
Fixed bug 2404700 - UseSingleton should not act on enums |
|
|