| Violation |
Line |
| A high number of imports can indicate a high degree of coupling within an object. |
34–645 |
| debug logging that involves string concatenation should be guarded with isDebugEnabled() checks |
152 |
| If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation |
157 |
| If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation |
180 |
| If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation |
203 |
| If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation |
245 |
| Substitute calls to size() == 0 (or size() != 0, size() > 0, size() < 1) with calls to isEmpty() |
278 |
| Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block |
290 |
| Substitute calls to size() == 0 (or size() != 0, size() > 0, size() < 1) with calls to isEmpty() |
341 |
| Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block |
353 |
| Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block |
401 |
| Avoid variables with short names like it |
441 |
| Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block |
461 |
| Avoid variables with short names like it |
496 |
| Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block |
516 |
| Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block |
557 |
| If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation |
604 |
| If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation |
619 |
