PMD Results
The following document contains the results of PMD 5.3.5.
Files
fr/paris/lutece/plugins/workflow/modules/reassignment/business/TaskReassignmentConfigDAO.java
| Violation |
Line |
| Use block level rather than method level synchronization |
60–75 |
fr/paris/lutece/plugins/workflow/modules/reassignment/service/ReassignmentPlugin.java
| Violation |
Line |
| All methods are static. Consider using a utility class instead. Alternatively, you could add a private constructor or make the class abstract to silence this warning. |
81–93 |
fr/paris/lutece/plugins/workflow/modules/reassignment/service/TaskReassignment.java
| Violation |
Line |
| A high number of imports can indicate a high degree of coupling within an object. |
34–255 |
| Document empty method |
119–120 |
| Avoid variables with short names like t |
160 |
fr/paris/lutece/plugins/workflow/modules/reassignment/web/ReassignmentTaskComponent.java
| Violation |
Line |
| The class 'ReassignmentTaskComponent' has a Cyclomatic Complexity of 5 (Highest = 13). |
74–352 |
| The class 'ReassignmentTaskComponent' has a Standard Cyclomatic Complexity of 4 (Highest = 11). |
74–352 |
| The class 'ReassignmentTaskComponent' has a Modified Cyclomatic Complexity of 4 (Highest = 11). |
74–352 |
| The method doSaveConfig() has an NPath complexity of 720 |
120–211 |
| The method 'doSaveConfig' has a Cyclomatic Complexity of 13. |
120–211 |
| The method 'doSaveConfig' has a Standard Cyclomatic Complexity of 11. |
120–211 |
| The method 'doSaveConfig' has a Modified Cyclomatic Complexity of 11. |
120–211 |
| Avoid declaring a variable if it is unreferenced before a possible exit point. |
125 |
| Avoid declaring a variable if it is unreferenced before a possible exit point. |
128 |
| Avoid declaring a variable if it is unreferenced before a possible exit point. |
220 |
| Avoid declaring a variable if it is unreferenced before a possible exit point. |
221 |
| If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation |
260 |
| If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation |
291 |
| If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation |
308 |
| If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation |
325 |
