PMD Results
The following document contains the results of PMD 5.3.2.
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 |
383–390 |
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'. |
77 |
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 |
131–132 |
com/helger/schematron/pure/bound/IPSBoundSchema.java
Violation |
Line |
Avoid unused imports such as 'com.helger.schematron.CSchematron' |
30 |
com/helger/schematron/pure/bound/xpath/PSXPathBoundSchema.java
Violation |
Line |
Do not use if statements that are always true or always false |
417 |
These nested if statements could be combined |
564–571 |
These nested if statements could be combined |
580–587 |
Do not use if statements that are always true or always false |
602 |
com/helger/schematron/pure/exchange/PSReader.java
Violation |
Line |
Do not use if statements that are always true or always false |
1261 |
com/helger/schematron/pure/model/PSActive.java
Violation |
Line |
These nested if statements could be combined |
63–64 |
These nested if statements could be combined |
86–87 |
com/helger/schematron/pure/model/PSAssertReport.java
Violation |
Line |
These nested if statements could be combined |
83–84 |
These nested if statements could be combined |
108–109 |
com/helger/schematron/pure/model/PSDiagnostic.java
Violation |
Line |
These nested if statements could be combined |
69–70 |
com/helger/schematron/pure/model/PSP.java
Violation |
Line |
These nested if statements could be combined |
66–67 |
com/helger/schematron/pure/model/PSTitle.java
Violation |
Line |
These nested if statements could be combined |
56–57 |
com/helger/schematron/pure/preprocess/PSPreprocessor.java
Violation |
Line |
These nested if statements could be combined |
498–499 |
com/helger/schematron/svrl/CSVRL.java
Violation |
Line |
Avoid unused private fields such as 's_aInstance'. |
54 |
com/helger/schematron/svrl/SVRLHelper.java
Violation |
Line |
Avoid unused private fields such as 's_aInstance'. |
49 |
com/helger/schematron/svrl/SVRLLocationBeautifierRegistry.java
Violation |
Line |
Avoid unused private fields such as 's_aInstance'. |
44 |
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 |
266 |
Do not use if statements that are always true or always false |
273 |