PMD Results
The following document contains the results of PMD 5.5.1.
Files
fr/paris/lutece/plugins/insertalbum/business/Image.java
| Violation |
Line |
| Avoid variables with short names like id |
38 |
| Document empty constructor |
41–43 |
| Avoid unnecessary constructors - the compiler will generate these for you |
41–43 |
| Avoid variables with short names like id |
50 |
fr/paris/lutece/plugins/insertalbum/business/InsertAlbumDAO.java
| Violation |
Line |
| Avoid unused imports such as 'java.sql.Timestamp' |
39 |
| Avoid unused imports such as 'java.sql.Timestamp' |
39 |
fr/paris/lutece/plugins/insertalbum/business/InsertAlbumHome.java
| Violation |
Line |
| A class which only has private constructors should be final |
44–60 |
fr/paris/lutece/plugins/insertalbum/web/InsertAlbumJspBean.java
| Violation |
Line |
| Private field 'PROPERTY_SLIDESHOW_LIST' could be made final; it is only initialized in the declaration or constructor. |
80 |
| The field name indicates a constant but its modifiers do not |
80 |
| If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation |
93 |
| If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation |
105 |
| Avoid declaring a variable if it is unreferenced before a possible exit point. |
105 |
| If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation |
141 |
| If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation |
178 |
| If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation |
220 |
| Substitute calls to size() == 0 (or size() != 0, size() > 0, size() < 1) with calls to isEmpty() |
224 |
