Le document suivant contient les résultats de PMD 5.3.5.
Violation | Ligne |
---|---|
A high number of imports can indicate a high degree of coupling within an object. | 34–329 |
Avoid unused imports such as 'java.io.Reader' | 65 |
Avoid unused imports such as 'java.io.Reader' | 65 |
Avoid unused imports such as 'java.io.StringReader' | 66 |
Avoid unused imports such as 'java.io.StringReader' | 66 |
Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 157 |
Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 217 |
Avoid throwing raw exception types. | 219 |
New exception is thrown in catch block, original stack trace may be lost | 219 |
Avoid printStackTrace(); use a logger call instead. | 269 |
Avoid printStackTrace(); use a logger call instead. | 271 |
Avoid unused method parameters such as 'plugin'. | 296 |
StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. | 300 |
StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. | 301 |
StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. | 302 |
StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. | 303 |
Avoid variables with short names like sb | 315 |