Résultats PMD
Le document suivant contient les résultats de PMD 5.5.1.
Fichiers
fr/paris/lutece/plugins/workflow/modules/editrecord/business/EditRecordDAO.java
| Violation |
Ligne |
| Use block level rather than method level synchronization |
62–74 |
fr/paris/lutece/plugins/workflow/modules/editrecord/business/EditRecordValueDAO.java
| Violation |
Ligne |
| Use block level rather than method level synchronization |
57–67 |
fr/paris/lutece/plugins/workflow/modules/editrecord/business/TaskEditRecordConfigDAO.java
| Violation |
Ligne |
| Use block level rather than method level synchronization |
58–70 |
fr/paris/lutece/plugins/workflow/modules/editrecord/service/EditRecordPlugin.java
| Violation |
Ligne |
| 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. |
46–59 |
fr/paris/lutece/plugins/workflow/modules/editrecord/service/EditRecordService.java
| Violation |
Ligne |
| A high number of imports can indicate a high degree of coupling within an object. |
34–690 |
| Possible God class (WMC=71, ATFD=137, TCC=0.0) |
34–690 |
fr/paris/lutece/plugins/workflow/modules/editrecord/service/TaskEditRecord.java
| Violation |
Ligne |
| Document empty method |
78–79 |
fr/paris/lutece/plugins/workflow/modules/editrecord/util/constants/EditRecordConstants.java
| Violation |
Ligne |
| Avoid variables with short names like ID |
45 |
fr/paris/lutece/plugins/workflow/modules/editrecord/web/EditRecordApp.java
| Violation |
Ligne |
| Private field '_editRecordService' could be made final; it is only initialized in the declaration or constructor. |
79 |
| If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation |
180 |
| These nested if statements could be combined |
220–229 |
| These nested if statements could be combined |
222–228 |
| Prefer StringBuffer over += for concatenating strings |
226 |
fr/paris/lutece/plugins/workflow/modules/editrecord/web/EditRecordTaskComponent.java
| Violation |
Ligne |
| If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation |
91 |
| If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation |
108 |
| If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation |
126 |
