Xavier Le Vourch c54f51b530 eclipse plugin reorganization
first of several commits to make sure the plugin can be generated in headless
mode from ant


git-svn-id: https://pmd.svn.sourceforge.net/svnroot/pmd/trunk@6502 51baf565-9d33-0410-a72c-fc3788e3496d
2008-09-25 23:18:33 +00:00

27 lines
1.1 KiB
Plaintext

###
### Short term (before next release)
###
###
### Medium term (following release, or soon after)
###
Refactor plugin projects. Do we really need 5 projects? Can we get by with 2?
There's a whole lot of layers, can we simply things a bit?
###
### Long term (wish list)
###
Upgrade plugin code to Java 5.
Allow import of a single rule from a RuleSet.
Warn if Import of a Rule results in a duplicate (what is a duplicate exactly?), allow option to Import All, Import Non Duplicates, or Cancel.
Warn if newly Added Rule has the name of an existing Rule.
Warn if non reference Rule looks like it might be a built-in PMD rule, and ask if replace with reference. On Add? On Import? On Upgrade?
Add Upgrade button, which will check current workspace RuleSet against PMD rules showing differences (new PMD rules, rules in
Allow checking to see what rules from PMD are missing (useful for upgrade process).
Allow auto-enabling newly added/imported Rules in Projects which are not using custom RuleSet, currently they are not selected.
Allow custom RuleSet editing to also take place at project level, instead of just at Workspace level.