The following document contains the results of PMD 5.3.5.
| Violation | Line |
|---|---|
| A high number of imports can indicate a high degree of coupling within an object. | 34–405 |
| Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 152 |
| Avoid declaring a variable if it is unreferenced before a possible exit point. | 171 |
| Avoid throwing raw exception types. | 205 |
| Avoid variables with short names like i | 290 |
| Avoid using while statements without curly braces | 292–293 |
| New exception is thrown in catch block, original stack trace may be lost | 324 |
| New exception is thrown in catch block, original stack trace may be lost | 328 |
| Avoid empty catch blocks | 345–347 |
| Avoid empty catch blocks | 348–350 |
| Avoid catching NullPointerException; consider removing the cause of the NPE. | 348 |
| Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 348 |
| StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. | 376 |
| StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. | 377 |
| StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. | 378 |
| StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. | 379 |
| StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. | 380 |
| StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. | 381 |
| Avoid variables with short names like sb | 400 |
