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–335 |
| The class 'MyDashboardCRMComponent' has a Standard Cyclomatic Complexity of 5 (Highest = 14). | 77–335 |
| The class 'MyDashboardCRMComponent' has a Modified Cyclomatic Complexity of 5 (Highest = 14). | 77–335 |
| The class 'MyDashboardCRMComponent' has a Cyclomatic Complexity of 5 (Highest = 18). | 77–335 |
| The method getDashboardData() has an NPath complexity of 9218 | 87–230 |
| Avoid really long methods. | 87–230 |
| The method 'getDashboardData' has a Standard Cyclomatic Complexity of 14. | 87–230 |
| The method 'getDashboardData' has a Cyclomatic Complexity of 18. | 87–230 |
| The method 'getDashboardData' has a Modified Cyclomatic Complexity of 14. | 87–230 |
| If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation | 99 |
| Deeply nested if..then statements are hard to read | 110–113 |
| Deeply nested if..then statements are hard to read | 121–124 |
| Deeply nested if..then statements are hard to read | 126–130 |
| Deeply nested if..then statements are hard to read | 136–140 |
| Deeply nested if..then statements are hard to read | 142–147 |
| Deeply nested if..then statements are hard to read | 149–153 |
| Deeply nested if..then statements are hard to read | 155–158 |
| Deeply nested if..then statements are hard to read | 162–167 |
| Deeply nested if..then statements are hard to read | 171–174 |
| Deeply nested if..then statements are hard to read | 178–181 |
| If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation | 187 |
| If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation | 188 |
| Avoid unused method parameters such as 'request'. | 255 |
| When instantiating a SimpleDateFormat object, specify a Locale | 258 |
| Avoid variables with short names like d | 261 |
| Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 267 |
| If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation | 306 |
| If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation | 320 |
