Is your feature request related to a problem? Please describe.
Currently there's a few things that are not so great with the test schema
regressionTest
to false, which is... weirdreinitializeRule
of test-code is useless. I can't see a reason not to reinitialize the rule.source-type
element, as we do the validation at runtime anyway. This means we wouldn't have to update the schema when we add/remove languages, which makes pmd easier to extend<expected-problems>0</expected-problems> <expected-messages> <message>1</message> </expected-messages>
throws a validation error, but the following doesn't
<expected-problems>1</expected-problems> <expected-linenumbers>1,2,3</expected-linenumbers> <expected-messages> <message>1</message> </expected-messages>
Describe the solution you'd like Update the schema and its parser to support focus
and disabled
attributes, deprecate useless things
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Some other things that we should keep in mind and fix later:
<rule-property>
element has ad-hoc syntax, instead of just reusing the syntax for <property>
that's from the ruleset schema. This will be awkward when the XSD for rulesets is updated ( [core] Implementation plan for property framework changes #1432)useAuxClasspath
attribute doesn't look useful. Related to [java] Improve rule tests with auxclasspath #2649RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4