Résultats PMD
Le document suivant contient les résultats de PMD 5.3.5.
Fichiers
fr/paris/lutece/plugins/mytasks/business/MyTaskDAO.java
| Violation |
Ligne |
| StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. |
174 |
| StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. |
175 |
fr/paris/lutece/plugins/mytasks/business/portlet/MyTasksPortlet.java
| Violation |
Ligne |
| It is a good practice to call super() in a constructor |
77–79 |
| Avoid unnecessary constructors - the compiler will generate these for you |
77–79 |
| Document empty constructor |
77–79 |
| Document empty method |
149–150 |
| Document empty method |
156–157 |
fr/paris/lutece/plugins/mytasks/business/portlet/MyTasksPortletDAO.java
| Violation |
Ligne |
| Document empty method |
50–51 |
| Document empty method |
57–58 |
| Document empty method |
75–76 |
fr/paris/lutece/plugins/mytasks/business/portlet/MyTasksPortletHome.java
| Violation |
Ligne |
| It is a good practice to call super() in a constructor |
61–63 |
| Avoid unnecessary constructors - the compiler will generate these for you |
61–63 |
| Document empty constructor |
61–63 |
| Singleton is not thread safe |
71–74 |
fr/paris/lutece/plugins/mytasks/service/MyTasksResourceIdService.java
| Violation |
Ligne |
| It is a good practice to call super() in a constructor |
62–65 |
| Avoid variables with short names like rt |
72 |
| Avoid variables with short names like p |
78 |
fr/paris/lutece/plugins/mytasks/service/MyTasksService.java
| Violation |
Ligne |
| It is a good practice to call super() in a constructor |
76–78 |
| Use block level rather than method level synchronization |
93–101 |
| StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. |
273 |
fr/paris/lutece/plugins/mytasks/service/parameter/MyTasksParameterService.java
| Violation |
Ligne |
| Use block level rather than method level synchronization |
62–70 |
| Document empty method |
76–77 |
fr/paris/lutece/plugins/mytasks/service/portlet/MyTasksPortletService.java
| Violation |
Ligne |
| Singleton is not thread safe |
57–60 |
| Document empty method |
69–70 |
fr/paris/lutece/plugins/mytasks/web/MyTasksAdminDashboardComponent.java
| Violation |
Ligne |
| If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation |
81 |
fr/paris/lutece/plugins/mytasks/web/MyTasksApp.java
| Violation |
Ligne |
| The class 'MyTasksApp' has a Cyclomatic Complexity of 4 (Highest = 10). |
71–500 |
| Private field '_myTasksService' could be made final; it is only initialized in the declaration or constructor. |
117 |
| If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation |
171 |
| 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 |
243 |
| The method 'doAddMyTask' has a Cyclomatic Complexity of 10. |
315–372 |
fr/paris/lutece/plugins/mytasks/web/portlet/MyTasksPortletJspBean.java
| Violation |
Ligne |
| If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation |
76 |
| If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation |
99 |
