The following document contains the results of PMD 6.13.0.
Rule | Violation | Line |
---|---|---|
ClassNamingConventions | The utility class name 'Utils' doesn't match '[A-Z][a-zA-Z0-9]+(Utils?|Helper|Home|Service)' | 66–286 |
FieldNamingConventions | The constant name '_rand' doesn't match '[A-Z][A-Z_0-9]*' | 72 |
Rule | Violation | Line |
---|---|---|
SystemPrintln | System.out.println is used | 102 |
SystemPrintln | System.out.println is used | 107 |
SystemPrintln | System.out.println is used | 110 |
Rule | Violation | Line |
---|---|---|
TestClassWithoutTestCases | This class name ends with Test but contains no test cases | 44–122 |
RedundantFieldInitializer | Avoid using redundant field initializer for '_bInit' | 50 |
JUnit4TestShouldUseBeforeAnnotation | JUnit 4 tests that set up tests should use the @Before annotation, JUnit5 tests should use @BeforeEach or @BeforeAll | 94–111 |
JUnit4TestShouldUseAfterAnnotation | JUnit 4 tests that clean up tests should use the @After annotation, JUnit5 tests should use @AfterEach or @AfterAll | 117–121 |
UselessOverridingMethod | Overriding method merely calls super | 118–121 |
Rule | Violation | Line |
---|---|---|
UseUtilityClass | 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. | 67–286 |
UseConcurrentHashMap | If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation | 82 |
UseDiamondOperator | Explicit type arguments can be replaced by Diamond Operator | 82 |
ShortVariable | Avoid variables with short names like is | 114 |
ShortVariable | Avoid variables with short names like in | 116 |
ConfusingTernary | Avoid if (x != y) ..; else ..; | 119–142 |
ShortVariable | Avoid variables with short names like n | 125 |
AssignmentInOperand | Avoid assignments in operands | 127 |
MissingBreakInSwitch | A switch statement does not contain a break | 225–241 |
CollapsibleIfStatements | These nested if statements could be combined | 234–237 |
AvoidDeeplyNestedIfStmts | Deeply nested if..then statements are hard to read | 234–237 |
Rule | Violation | Line |
---|---|---|
UseVarargs | Consider using varargs for methods or constructors which take an array the last parameter. | 125 |
Rule | Violation | Priority | Line |
---|---|---|---|
TestClassWithoutTestCases | This class name ends with Test but contains no test cases | 3 | 44–122 |
RedundantFieldInitializer | Avoid using redundant field initializer for '_bInit' | 3 | 50 |
JUnit4TestShouldUseBeforeAnnotation | JUnit 4 tests that set up tests should use the @Before annotation, JUnit5 tests should use @BeforeEach or @BeforeAll | 3 | 94–111 |
SystemPrintln | System.out.println is used | 2 | 102 |
SystemPrintln | System.out.println is used | 2 | 107 |
SystemPrintln | System.out.println is used | 2 | 110 |
JUnit4TestShouldUseAfterAnnotation | JUnit 4 tests that clean up tests should use the @After annotation, JUnit5 tests should use @AfterEach or @AfterAll | 3 | 117–121 |
UselessOverridingMethod | Overriding method merely calls super | 3 | 118–121 |
Rule | Violation | Priority | Line |
---|---|---|---|
UseVarargs | Consider using varargs for methods or constructors which take an array the last parameter. | 4 | 125 |
Rule | Violation | Priority | Line |
---|---|---|---|
ClassNamingConventions | The utility class name 'Utils' doesn't match '[A-Z][a-zA-Z0-9]+(Utils?|Helper|Home|Service)' | 1 | 66–286 |
UseUtilityClass | 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. | 3 | 67–286 |
FieldNamingConventions | The constant name '_rand' doesn't match '[A-Z][A-Z_0-9]*' | 1 | 72 |
UseConcurrentHashMap | If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation | 3 | 82 |
UseDiamondOperator | Explicit type arguments can be replaced by Diamond Operator | 3 | 82 |
ShortVariable | Avoid variables with short names like is | 3 | 114 |
ShortVariable | Avoid variables with short names like in | 3 | 116 |
ConfusingTernary | Avoid if (x != y) ..; else ..; | 3 | 119–142 |
ShortVariable | Avoid variables with short names like n | 3 | 125 |
AssignmentInOperand | Avoid assignments in operands | 3 | 127 |
MissingBreakInSwitch | A switch statement does not contain a break | 3 | 225–241 |
CollapsibleIfStatements | These nested if statements could be combined | 3 | 234–237 |
AvoidDeeplyNestedIfStmts | Deeply nested if..then statements are hard to read | 3 | 234–237 |