Résultats PMD
Le document suivant contient les résultats de PMD 5.3.5.
Fichiers
fr/paris/lutece/plugins/workflow/modules/alert/business/AlertDAO.java
| Violation |
Ligne |
| Use block level rather than method level synchronization |
61–73 |
fr/paris/lutece/plugins/workflow/modules/alert/business/TaskAlertConfigDAO.java
| Violation |
Ligne |
| Use block level rather than method level synchronization |
60–75 |
fr/paris/lutece/plugins/workflow/modules/alert/service/AlertPlugin.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. |
47–59 |
fr/paris/lutece/plugins/workflow/modules/alert/service/AlertService.java
| Violation |
Ligne |
| A high number of imports can indicate a high degree of coupling within an object. |
34–489 |
| Possible God class (WMC=48, ATFD=100, TCC=0.0) |
34–489 |
| Private field '_listAcceptedEntryTypesDate' could be made final; it is only initialized in the declaration or constructor. |
90 |
| Deeply nested if..then statements are hard to read |
206–210 |
| Deeply nested if..then statements are hard to read |
383–386 |
| StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. |
453 |
| StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. |
454 |
| StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. |
455 |
| StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. |
456 |
| StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. |
457 |
fr/paris/lutece/plugins/workflow/modules/alert/service/TaskAlert.java
| Violation |
Ligne |
| Deeply nested if..then statements are hard to read |
106–119 |
fr/paris/lutece/plugins/workflow/modules/alert/service/daemon/AlertCleanerDaemon.java
| Violation |
Ligne |
| StringBuffer constructor is initialized with size 16, but has at least 80 characters appended. |
64 |
fr/paris/lutece/plugins/workflow/modules/alert/service/daemon/AlertDaemon.java
| Violation |
Ligne |
| StringBuffer constructor is initialized with size 16, but has at least 76 characters appended. |
66 |
| Deeply nested if..then statements are hard to read |
93–98 |
fr/paris/lutece/plugins/workflow/modules/alert/util/constants/AlertConstants.java
| Violation |
Ligne |
| Avoid variables with short names like ID |
46 |
fr/paris/lutece/plugins/workflow/modules/alert/util/validation/AlertConfigValidator.java
| Violation |
Ligne |
| Document empty method |
57–58 |
fr/paris/lutece/plugins/workflow/modules/alert/web/AlertTaskComponent.java
| Violation |
Ligne |
| If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation |
75 |
