PMD Results
The following document contains the results of PMD 6.4.0.
Files
com/helger/schematron/AbstractSchematronResource.java
Violation |
Priority |
Line |
Do not use if statements that are always true or always false |
3 |
132 |
Avoid empty catch blocks |
3 |
165–169 |
com/helger/schematron/CSchematron.java
Violation |
Priority |
Line |
Avoid unused private fields such as 's_aInstance'. |
3 |
44 |
com/helger/schematron/CSchematronXML.java
Violation |
Priority |
Line |
Avoid unused private fields such as 's_aInstance'. |
3 |
81 |
com/helger/schematron/SchematronHelper.java
Violation |
Priority |
Line |
Avoid unused private fields such as 's_aInstance'. |
3 |
70 |
These nested if statements could be combined |
3 |
369–376 |
com/helger/schematron/SchematronResourceHelper.java
Violation |
Priority |
Line |
Avoid unused private fields such as 's_aInstance'. |
3 |
54 |
com/helger/schematron/pure/SchematronResourcePure.java
Violation |
Priority |
Line |
Avoid empty catch blocks |
3 |
321–324 |
com/helger/schematron/pure/binding/PSQueryBindingRegistry.java
Violation |
Priority |
Line |
Avoid unused private fields such as 's_aInstance'. |
3 |
74 |
com/helger/schematron/pure/binding/xpath/CXPath.java
Violation |
Priority |
Line |
Avoid unused private fields such as 's_aInstance'. |
3 |
35 |
com/helger/schematron/pure/binding/xpath/PSXPathVariables.java
Violation |
Priority |
Line |
These nested if statements could be combined |
3 |
128–129 |
com/helger/schematron/pure/bound/xpath/PSXPathBoundSchema.java
Violation |
Priority |
Line |
These nested if statements could be combined |
3 |
563–571 |
These nested if statements could be combined |
3 |
580–588 |
Do not use if statements that are always true or always false |
3 |
603 |
com/helger/schematron/pure/model/PSActive.java
Violation |
Priority |
Line |
These nested if statements could be combined |
3 |
64–65 |
These nested if statements could be combined |
3 |
87–88 |
com/helger/schematron/pure/model/PSAssertReport.java
Violation |
Priority |
Line |
These nested if statements could be combined |
3 |
92–93 |
These nested if statements could be combined |
3 |
117–118 |
com/helger/schematron/pure/model/PSDiagnostic.java
Violation |
Priority |
Line |
These nested if statements could be combined |
3 |
76–77 |
com/helger/schematron/pure/model/PSDir.java
Violation |
Priority |
Line |
Avoid modifiers which are implied by the context |
3 |
55–79 |
com/helger/schematron/pure/model/PSP.java
Violation |
Priority |
Line |
These nested if statements could be combined |
3 |
67–68 |
com/helger/schematron/pure/model/PSRichGroup.java
Violation |
Priority |
Line |
Avoid modifiers which are implied by the context |
3 |
42–66 |
com/helger/schematron/pure/model/PSTitle.java
Violation |
Priority |
Line |
These nested if statements could be combined |
3 |
55–56 |
com/helger/schematron/pure/preprocess/PSPreprocessor.java
Violation |
Priority |
Line |
Ternary operators that can be simplified with || or && |
3 |
290 |
These nested if statements could be combined |
3 |
533–534 |
com/helger/schematron/saxon/SchematronTransformerFactory.java
Violation |
Priority |
Line |
Do not use if statements that are always true or always false |
3 |
100 |
Do not use if statements that are always true or always false |
3 |
102 |
Do not use if statements that are always true or always false |
3 |
104 |
com/helger/schematron/svrl/CSVRL.java
Violation |
Priority |
Line |
Avoid unused private fields such as 's_aInstance'. |
3 |
57 |
com/helger/schematron/svrl/SVRLHelper.java
Violation |
Priority |
Line |
Avoid unused private fields such as 's_aInstance'. |
3 |
52 |
com/helger/schematron/svrl/SVRLLocationBeautifierRegistry.java
Violation |
Priority |
Line |
Avoid unused private fields such as 's_aInstance'. |
3 |
42 |
com/helger/schematron/svrl/SVRLReader.java
Violation |
Priority |
Line |
Avoid unused private fields such as 's_aInstance'. |
3 |
43 |
com/helger/schematron/svrl/SVRLWriter.java
Violation |
Priority |
Line |
Avoid unused private fields such as 's_aInstance'. |
3 |
42 |
com/helger/schematron/xslt/AbstractSchematronXSLTBasedResource.java
Violation |
Priority |
Line |
Do not use if statements that are always true or always false |
3 |
257 |
These nested if statements could be combined |
3 |
258–279 |
Do not use if statements that are always true or always false |
3 |
264 |
Do not use if statements that are always true or always false |
3 |
266 |
Do not use if statements that are always true or always false |
3 |
273 |
Do not use if statements that are always true or always false |
3 |
275 |
Do not use if statements that are always true or always false |
3 |
277 |
com/helger/schematron/xslt/SCHTransformerCustomizer.java
Violation |
Priority |
Line |
Avoid modifiers which are implied by the context |
3 |
40–45 |