Résultats PMD
Le document suivant contient les résultats de PMD 6.13.0.
Violations By Priority
Priority 1
fr/paris/lutece/plugins/workflow/modules/formsextend/service/DashboardNotificationService.java
fr/paris/lutece/plugins/workflow/modules/formsextend/util/FormsExtendConstants.java
Rule |
Violation |
Ligne |
ClassNamingConventions |
The utility class name 'FormsExtendConstants' doesn't match '[A-Z][a-zA-Z0-9]+(Utils?|Helper|Home|Service)' |
41–57 |
Priority 3
fr/paris/lutece/plugins/workflow/modules/formsextend/business/MassNotificationTaskConfig.java
fr/paris/lutece/plugins/workflow/modules/formsextend/service/DashboardNotificationService.java
fr/paris/lutece/plugins/workflow/modules/formsextend/service/MassNotificationService.java
Rule |
Violation |
Ligne |
ExcessiveImports |
A high number of imports can indicate a high degree of coupling within an object. |
34–364 |
DefaultPackage |
Use explicit scoping instead of the default package private level |
110–112 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the _resourceWorkflowService field if you want a default access modifier |
112 |
UseConcurrentHashMap |
If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation |
160 |
UseConcurrentHashMap |
If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation |
254 |
ConfusingTernary |
Avoid if (x != y) ..; else ..; |
272–282 |
UseConcurrentHashMap |
If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation |
292 |
fr/paris/lutece/plugins/workflow/modules/formsextend/util/FormsExtendConstants.java
Rule |
Violation |
Ligne |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
52 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
53 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
54 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
55 |
fr/paris/lutece/plugins/workflow/modules/formsextend/web/MassNotificationTaskComponent.java
Rule |
Violation |
Ligne |
UseConcurrentHashMap |
If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation |
84 |
Priority 4
fr/paris/lutece/plugins/workflow/modules/formsextend/business/MassNotificationTaskConfig.java
Rule |
Violation |
Ligne |
UseVarargs |
Consider using varargs for methods or constructors which take an array the last parameter. |
140 |
UseVarargs |
Consider using varargs for methods or constructors which take an array the last parameter. |
225 |
fr/paris/lutece/plugins/workflow/modules/formsextend/service/MassNotificationService.java
Rule |
Violation |
Ligne |
UnusedImports |
Avoid unused imports such as 'fr.paris.lutece.portal.service.util.AppPathService' |
84 |
Fichiers
fr/paris/lutece/plugins/workflow/modules/formsextend/business/MassNotificationTaskConfig.java
fr/paris/lutece/plugins/workflow/modules/formsextend/service/DashboardNotificationService.java
fr/paris/lutece/plugins/workflow/modules/formsextend/service/MassNotificationService.java
Rule |
Violation |
Priority |
Ligne |
ExcessiveImports |
A high number of imports can indicate a high degree of coupling within an object. |
3 |
34–364 |
UnusedImports |
Avoid unused imports such as 'fr.paris.lutece.portal.service.util.AppPathService' |
4 |
84 |
DefaultPackage |
Use explicit scoping instead of the default package private level |
3 |
110–112 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the _resourceWorkflowService field if you want a default access modifier |
3 |
112 |
UseConcurrentHashMap |
If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation |
3 |
160 |
UseConcurrentHashMap |
If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation |
3 |
254 |
ConfusingTernary |
Avoid if (x != y) ..; else ..; |
3 |
272–282 |
UseConcurrentHashMap |
If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation |
3 |
292 |
fr/paris/lutece/plugins/workflow/modules/formsextend/util/FormsExtendConstants.java
Rule |
Violation |
Priority |
Ligne |
ClassNamingConventions |
The utility class name 'FormsExtendConstants' doesn't match '[A-Z][a-zA-Z0-9]+(Utils?|Helper|Home|Service)' |
1 |
41–57 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
52 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
53 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
54 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
55 |
fr/paris/lutece/plugins/workflow/modules/formsextend/web/MassNotificationTaskComponent.java
Rule |
Violation |
Priority |
Ligne |
UseConcurrentHashMap |
If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation |
3 |
84 |