PMD Results
The following document contains the results of PMD 5.5.1.
Files
fr/paris/lutece/plugins/workflow/modules/reply/business/config/TaskReplyConfig.java
| Violation |
Line |
| Avoid unused imports such as 'javax.validation.constraints.Min' |
37 |
| Avoid unused imports such as 'javax.validation.constraints.Min' |
37 |
| Avoid unused imports such as 'javax.validation.constraints.NotNull' |
38 |
| Avoid unused imports such as 'javax.validation.constraints.NotNull' |
38 |
fr/paris/lutece/plugins/workflow/modules/reply/business/task/Reply.java
| Violation |
Line |
| Avoid unused imports such as 'java.util.List' |
36 |
| Avoid unused imports such as 'java.util.List' |
36 |
fr/paris/lutece/plugins/workflow/modules/reply/business/task/ReplyDAO.java
| Violation |
Line |
| Use block level rather than method level synchronization |
60–71 |
fr/paris/lutece/plugins/workflow/modules/reply/service/IReplyService.java
| Violation |
Line |
| Avoid unused imports such as 'fr.paris.lutece.util.ReferenceList' |
44 |
| Avoid unused imports such as 'fr.paris.lutece.util.ReferenceList' |
44 |
fr/paris/lutece/plugins/workflow/modules/reply/service/ReplyPlugin.java
| Violation |
Line |
| 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/reply/service/ReplyService.java
| Violation |
Line |
| Avoid unused private fields such as '_stateService'. |
65 |
| Avoid unused private fields such as '_actionService'. |
67 |
fr/paris/lutece/plugins/workflow/modules/reply/service/provider/ReplyMarkerProvider.java
| Violation |
Line |
| Avoid variables with short names like ID |
58 |
fr/paris/lutece/plugins/workflow/modules/reply/service/task/TaskReply.java
| Violation |
Line |
| Avoid unused private fields such as '_user'. |
65 |
| Document empty method |
87–88 |
fr/paris/lutece/plugins/workflow/modules/reply/service/taskinfo/ReplyTaskInfoProvider.java
| Violation |
Line |
| Avoid using if statements without curly braces |
78–79 |
fr/paris/lutece/plugins/workflow/modules/reply/util/constants/ReplyConstants.java
| Violation |
Line |
| Avoid variables with short names like ID |
45 |
fr/paris/lutece/plugins/workflow/modules/reply/web/task/TaskReplyComponent.java
| Violation |
Line |
| If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation |
88 |
| If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation |
107 |
| Avoid using if statements without curly braces |
123–124 |
| Avoid using if statements without curly braces |
129–130 |
| Prefer StringBuffer over += for concatenating strings |
130 |
| Avoid declaring a variable if it is unreferenced before a possible exit point. |
144 |
| Avoid declaring a variable if it is unreferenced before a possible exit point. |
145 |
