Résultats PMD
Le document suivant contient les résultats de PMD 5.3.5.
Fichiers
fr/paris/lutece/plugins/wrapper/business/Wrapper.java
| Violation |
Ligne |
| Avoid unnecessary constructors - the compiler will generate these for you |
65–67 |
| Document empty constructor |
65–67 |
| Singleton is not thread safe |
75–79 |
fr/paris/lutece/plugins/wrapper/business/WrapperHome.java
| Violation |
Ligne |
| Avoid unused imports such as 'fr.paris.lutece.portal.business.indexeraction.IndexerAction' |
36 |
| Avoid unused imports such as 'fr.paris.lutece.portal.business.indexeraction.IndexerAction' |
36 |
| Avoid unused imports such as 'fr.paris.lutece.portal.service.search.IndexationService' |
38 |
| Avoid unused imports such as 'fr.paris.lutece.portal.service.search.IndexationService' |
38 |
| Avoid unused imports such as 'fr.paris.lutece.portal.service.util.AppPropertiesService' |
40 |
| Avoid unused imports such as 'fr.paris.lutece.portal.service.util.AppPropertiesService' |
40 |
| A class which only has private constructors should be final |
49–142 |
fr/paris/lutece/plugins/wrapper/service/WrapperWorkgroupRemovalListener.java
| Violation |
Ligne |
| Avoid unnecessary constructors - the compiler will generate these for you |
88–90 |
| Document empty constructor |
88–90 |
fr/paris/lutece/plugins/wrapper/web/WrapperApp.java
| Violation |
Ligne |
| Avoid unused private fields such as 'PARAMETER_WRAPPER'. |
67 |
| Avoid unnecessary constructors - the compiler will generate these for you |
94–96 |
| Document empty constructor |
94–96 |
fr/paris/lutece/plugins/wrapper/web/WrapperJspBean.java
| Violation |
Ligne |
| Perhaps '_nDefaultItemsPerPage' could be replaced by a local variable. |
109 |
| If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation |
133 |
| Do not add empty strings |
134 |
| If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation |
153 |
| Avoid declaring a variable if it is unreferenced before a possible exit point. |
173 |
| Avoid declaring a variable if it is unreferenced before a possible exit point. |
174 |
| Avoid declaring a variable if it is unreferenced before a possible exit point. |
175 |
| Avoid declaring a variable if it is unreferenced before a possible exit point. |
176 |
| Avoid declaring a variable if it is unreferenced before a possible exit point. |
177 |
| If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation |
239 |
