The following document contains the results of PMD 5.5.1.
| Violation | Line |
|---|---|
| Do not use if statements that are always true or always false | 137 |
| Avoid empty catch blocks | 158–162 |
| Violation | Line |
|---|---|
| Avoid unused private fields such as 's_aInstance'. | 44 |
| Violation | Line |
|---|---|
| Avoid unused private fields such as 's_aInstance'. | 81 |
| Violation | Line |
|---|---|
| Unnecessary final modifier in final class | 56–59 |
| Unnecessary final modifier in final class | 61–64 |
| Unnecessary final modifier in final class | 72–75 |
| Unnecessary final modifier in final class | 77–81 |
| Unnecessary final modifier in final class | 89–92 |
| Unnecessary final modifier in final class | 94–98 |
| Violation | Line |
|---|---|
| Avoid unused private fields such as 's_aInstance'. | 70 |
| These nested if statements could be combined | 369–376 |
| Violation | Line |
|---|---|
| Avoid unused private fields such as 's_aInstance'. | 54 |
| Violation | Line |
|---|---|
| Avoid empty catch blocks | 321–324 |
| Violation | Line |
|---|---|
| Avoid unused private fields such as 's_aInstance'. | 74 |
| Violation | Line |
|---|---|
| Avoid unused private fields such as 's_aInstance'. | 35 |
| Violation | Line |
|---|---|
| These nested if statements could be combined | 128–129 |
| Violation | Line |
|---|---|
| Avoid unused imports such as 'com.helger.schematron.CSchematron' | 28 |
| Violation | Line |
|---|---|
| Do not use if statements that are always true or always false | 424 |
| These nested if statements could be combined | 575–583 |
| These nested if statements could be combined | 592–600 |
| Do not use if statements that are always true or always false | 615 |
| Violation | Line |
|---|---|
| These nested if statements could be combined | 64–65 |
| These nested if statements could be combined | 87–88 |
| Violation | Line |
|---|---|
| These nested if statements could be combined | 92–93 |
| These nested if statements could be combined | 117–118 |
| Violation | Line |
|---|---|
| These nested if statements could be combined | 76–77 |
| Violation | Line |
|---|---|
| These nested if statements could be combined | 67–68 |
| Violation | Line |
|---|---|
| These nested if statements could be combined | 55–56 |
| Violation | Line |
|---|---|
| Ternary operators that can be simplified with || or && | 258 |
| These nested if statements could be combined | 501–502 |
| Violation | Line |
|---|---|
| Do not use if statements that are always true or always false | 100 |
| Do not use if statements that are always true or always false | 102 |
| Do not use if statements that are always true or always false | 104 |
| Violation | Line |
|---|---|
| Avoid unused private fields such as 's_aInstance'. | 63 |
| Violation | Line |
|---|---|
| Avoid unused private fields such as 's_aInstance'. | 47 |
| Violation | Line |
|---|---|
| Avoid unused private fields such as 's_aInstance'. | 42 |
| Violation | Line |
|---|---|
| Avoid unused private fields such as 's_aInstance'. | 41 |
| Violation | Line |
|---|---|
| Avoid unused private fields such as 's_aInstance'. | 41 |
| Violation | Line |
|---|---|
| Do not use if statements that are always true or always false | 248 |
| These nested if statements could be combined | 249–270 |
| Do not use if statements that are always true or always false | 255 |
| Do not use if statements that are always true or always false | 257 |
| Do not use if statements that are always true or always false | 264 |
| 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 | 268 |