Le document suivant contient les résultats de PMD 6.13.0.
| Rule | Violation | Ligne |
|---|---|---|
| ClassNamingConventions | The utility class name 'NotificationConstants' doesn't match '[A-Z][a-zA-Z0-9]+(Utils?|Helper|Home|Service)' | 41–70 |
| Rule | Violation | Ligne |
|---|---|---|
| UseStringBufferForStringAppends | Prefer StringBuilder (non-synchronized) or StringBuffer (synchronized) over += for concatenating strings | 169 |
| Rule | Violation | Ligne |
|---|---|---|
| DefaultPackage | Use explicit scoping instead of the default package private level | 54–55 |
| CommentDefaultAccessModifier | To avoid mistakes add a comment at the beginning of the _notificationDAO field if you want a default access modifier | 55 |
| Rule | Violation | Ligne |
|---|---|---|
| ImmutableField | Private field '_objectMapper' could be made final; it is only initialized in the declaration or constructor. | 75 |
| CommentRequired | Public method and constructor comments are required | 81–102 |
| CommentRequired | Public method and constructor comments are required | 108–131 |
| CommentRequired | Public method and constructor comments are required | 137–155 |
| CommentRequired | Public method and constructor comments are required | 161–182 |
| CommentRequired | Public method and constructor comments are required | 188–201 |
| Rule | Violation | Ligne |
|---|---|---|
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 51 |
| 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. | 55 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 56 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 57 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 59 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 60 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 62 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 64 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 66 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 68 |
| Rule | Violation | Ligne |
|---|---|---|
| UseConcurrentHashMap | If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation | 92 |
| ConfusingTernary | Avoid if (x != y) ..; else ..; | 96–98 |
| AddEmptyString | Do not add empty strings | 112 |
| Rule | Violation | Ligne |
|---|---|---|
| UseConcurrentHashMap | If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation | 88 |
| Rule | Violation | Ligne |
|---|---|---|
| ImmutableField | Private field '_notificationService' could be made final; it is only initialized in the declaration or constructor. | 70 |
| LinguisticNaming | Linguistics Antipattern - The setter 'setStatusRead' should not return any type except void linguistically | 73–90 |
| CommentRequired | Public method and constructor comments are required | 73–90 |
| Rule | Violation | Priority | Ligne |
|---|---|---|---|
| UseStringBufferForStringAppends | Prefer StringBuilder (non-synchronized) or StringBuffer (synchronized) over += for concatenating strings | 3 | 169 |
| Rule | Violation | Priority | Ligne |
|---|---|---|---|
| DefaultPackage | Use explicit scoping instead of the default package private level | 3 | 54–55 |
| CommentDefaultAccessModifier | To avoid mistakes add a comment at the beginning of the _notificationDAO field if you want a default access modifier | 3 | 55 |
| Rule | Violation | Priority | Ligne |
|---|---|---|---|
| ImmutableField | Private field '_objectMapper' could be made final; it is only initialized in the declaration or constructor. | 3 | 75 |
| CommentRequired | Public method and constructor comments are required | 3 | 81–102 |
| CommentRequired | Public method and constructor comments are required | 3 | 108–131 |
| CommentRequired | Public method and constructor comments are required | 3 | 137–155 |
| CommentRequired | Public method and constructor comments are required | 3 | 161–182 |
| CommentRequired | Public method and constructor comments are required | 3 | 188–201 |
| Rule | Violation | Priority | Ligne |
|---|---|---|---|
| ClassNamingConventions | The utility class name 'NotificationConstants' doesn't match '[A-Z][a-zA-Z0-9]+(Utils?|Helper|Home|Service)' | 1 | 41–70 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 3 | 51 |
| 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 | 55 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 3 | 56 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 3 | 57 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 3 | 59 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 3 | 60 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 3 | 62 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 3 | 64 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 3 | 66 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 3 | 68 |
| Rule | Violation | Priority | Ligne |
|---|---|---|---|
| UseConcurrentHashMap | If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation | 3 | 92 |
| ConfusingTernary | Avoid if (x != y) ..; else ..; | 3 | 96–98 |
| AddEmptyString | Do not add empty strings | 3 | 112 |
| Rule | Violation | Priority | Ligne |
|---|---|---|---|
| UseConcurrentHashMap | If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation | 3 | 88 |
| Rule | Violation | Priority | Ligne |
|---|---|---|---|
| ImmutableField | Private field '_notificationService' could be made final; it is only initialized in the declaration or constructor. | 3 | 70 |
| LinguisticNaming | Linguistics Antipattern - The setter 'setStatusRead' should not return any type except void linguistically | 3 | 73–90 |
| CommentRequired | Public method and constructor comments are required | 3 | 73–90 |
