* Colour syntax highlighting for all relevant editors & example viewers.
* User-selectable marker shapes and colours, violation decorators in the navigator tree
* New AST view and related XPath test editor
* Rule search (page form only, non-functional)
Disabled Quickfix views until its ready
Zapped several nevarious bugs in previous functionality
Note: for the time being, violation errors will not appear in the Problems
page. There is a conflict between having unique markers and 'standard'
error markers that denote inclusion in the error page. Will check out
the use of annotations to deal with this...
For evaluation:
The size and scope of the rule editor is (I believe) outgrowing its
placement within its preference page and it needs to be parked within
it own view. Besides, tracking all the edits being made to the rules
goes beyond what the pref pages can handle (i.e. apply/cancel...
which never worked properly for the rules in any case)
To that end, I've copied the rule table into its own view for now and
left the one in the preference page as is so we can compare & contrast.
Only one will remain by the time the best approach is chosen.
git-svn-id: https://pmd.svn.sourceforge.net/svnroot/pmd/trunk@7115 51baf565-9d33-0410-a72c-fc3788e3496d
1) Allow the PMD context menu on any File type, not just *.java.
2) Modify some places which check for a .java extension to _not_ do so.
3) Modify some places to check with the PMDEngine whether a File "applies" (e.g. is it for a Language which is understood by PMD and are there any Rules in the RuleSet for that Language).
Expand the Rule table to have a Language column in the 1st column. The table setup in this plugin/SWT still *sucks* as bad I remember it being the last time I added columns.
With these changes I can get both JS and XML Rules to work. Violations show up, and for JS, I can be brought to the proper line number in the code!
Also fixed and issue with this plugin looking for a "maxViolations" property on the Rules, which given PMD 5.0 changes to require a propery to exist to ask for a value... needed some tweaking to first check for the value on the Rule. More verbose, but a safer API than the Wild West style of pre-5.0.
The Rule Editor needs some work to account for the new structure of Rules in PMD 5.0. Currently any Rule it creates causes things to blow up due to missing Language. Easy enough to fix, but it's just the 1st of several things needing to be corrected.
git-svn-id: https://pmd.svn.sourceforge.net/svnroot/pmd/trunk@6742 51baf565-9d33-0410-a72c-fc3788e3496d
