PMD Results
The following document contains the results of PMD 5.3.5.
Files
com/helger/schematron/CSchematron.java
Violation |
Line |
Avoid unused private fields such as 's_aInstance'. |
51 |
com/helger/schematron/CSchematronXML.java
Violation |
Line |
Avoid unused private fields such as 's_aInstance'. |
81 |
com/helger/schematron/SchematronHelper.java
Violation |
Line |
Avoid unused private fields such as 's_aInstance'. |
68 |
These nested if statements could be combined |
385–392 |
com/helger/schematron/SchematronResourceHelper.java
Violation |
Line |
Avoid unused private fields such as 's_aInstance'. |
53 |
com/helger/schematron/pure/SchematronResourcePure.java
Violation |
Line |
Avoid empty catch blocks |
291–294 |
com/helger/schematron/pure/binding/PSQueryBindingRegistry.java
Violation |
Line |
Avoid unused private fields such as 's_aInstance'. |
74 |
com/helger/schematron/pure/binding/xpath/CXPath.java
Violation |
Line |
Avoid unused private fields such as 's_aInstance'. |
35 |
com/helger/schematron/pure/binding/xpath/PSXPathVariables.java
Violation |
Line |
These nested if statements could be combined |
128–129 |
com/helger/schematron/pure/bound/IPSBoundSchema.java
Violation |
Line |
Avoid unused imports such as 'com.helger.schematron.CSchematron' |
28 |
com/helger/schematron/pure/bound/xpath/PSXPathBoundSchema.java
Violation |
Line |
Do not use if statements that are always true or always false |
424 |
These nested if statements could be combined |
572–580 |
These nested if statements could be combined |
589–597 |
Do not use if statements that are always true or always false |
612 |
com/helger/schematron/pure/exchange/PSReader.java
Violation |
Line |
Do not use if statements that are always true or always false |
1166 |
com/helger/schematron/pure/model/PSActive.java
Violation |
Line |
These nested if statements could be combined |
64–65 |
These nested if statements could be combined |
87–88 |
com/helger/schematron/pure/model/PSAssertReport.java
Violation |
Line |
These nested if statements could be combined |
92–93 |
These nested if statements could be combined |
117–118 |
com/helger/schematron/pure/model/PSDiagnostic.java
Violation |
Line |
These nested if statements could be combined |
76–77 |
com/helger/schematron/pure/model/PSP.java
Violation |
Line |
These nested if statements could be combined |
67–68 |
com/helger/schematron/pure/model/PSTitle.java
Violation |
Line |
These nested if statements could be combined |
55–56 |
com/helger/schematron/pure/preprocess/PSPreprocessor.java
Violation |
Line |
These nested if statements could be combined |
499–500 |
com/helger/schematron/svrl/CSVRL.java
Violation |
Line |
Avoid unused private fields such as 's_aInstance'. |
61 |
com/helger/schematron/svrl/SVRLHelper.java
Violation |
Line |
Avoid unused private fields such as 's_aInstance'. |
47 |
com/helger/schematron/svrl/SVRLLocationBeautifierRegistry.java
Violation |
Line |
Avoid unused private fields such as 's_aInstance'. |
43 |
com/helger/schematron/svrl/SVRLReader.java
Violation |
Line |
Avoid unused private fields such as 's_aInstance'. |
41 |
com/helger/schematron/svrl/SVRLWriter.java
Violation |
Line |
Avoid unused private fields such as 's_aInstance'. |
41 |
com/helger/schematron/xslt/AbstractSchematronXSLTBasedResource.java
Violation |
Line |
Do not use if statements that are always true or always false |
262 |
Do not use if statements that are always true or always false |
269 |