PMD Results
The following document contains the results of PMD 4.2.5.
Files
junitx/ddtunit/DDTTestCase.java
Violation | Line |
---|
Avoid empty catch blocks | 92 - 94 |
Avoid empty finally blocks | 186 - 187 |
junitx/ddtunit/InternalLogger.java
Violation | Line |
---|
Avoid empty if statements | 63 - 70 |
junitx/ddtunit/data/AssertObject.java
Violation | Line |
---|
Avoid unused private methods such as 'validateSubType(Class)'. | 107 |
Avoid empty catch blocks | 116 - 118 |
junitx/ddtunit/data/ComparableRange.java
Violation | Line |
---|
These nested if statements could be combined | 71 - 74 |
These nested if statements could be combined | 95 - 98 |
These nested if statements could be combined | 137 - 140 |
junitx/ddtunit/data/ObjectAsserter.java
Violation | Line |
---|
These nested if statements could be combined | 263 - 269 |
Avoid unused method parameters such as 'assertEx'. | 324 - 340 |
junitx/ddtunit/data/db/DbDataRestorer.java
Violation | Line |
---|
Avoid empty catch blocks | 131 - 133 |
Avoid unused local variables such as 'type'. | 178 |
Avoid empty catch blocks | 245 - 247 |
Always check the return of one of the navigation method (next,previous,first,last) of a ResultSet. | 288 |
Avoid empty catch blocks | 299 - 301 |
junitx/ddtunit/data/processing/ActionBase.java
Violation | Line |
---|
These nested if statements could be combined | 526 - 528 |
junitx/ddtunit/data/processing/AttributeListCreatorAction.java
Violation | Line |
---|
Avoid empty if statements | 110 - 112 |
junitx/ddtunit/data/processing/BeanCreatorAction.java
Violation | Line |
---|
Avoid unused local variables such as 'param'. | 181 |
junitx/ddtunit/data/processing/CollectionCreatorAction.java
Violation | Line |
---|
These nested if statements could be combined | 113 - 115 |
Avoid empty if statements | 191 - 193 |
These nested if statements could be combined | 255 - 257 |
junitx/ddtunit/data/processing/DateCreatorAction.java
Violation | Line |
---|
Avoid unused private fields such as 'PROP_SYSTIME'. | 184 |
Avoid unused local variables such as 'name'. | 221 |
junitx/ddtunit/data/processing/MapCreatorAction.java
Violation | Line |
---|
Avoid unused imports such as 'java.util.Collection' | 40 |
Avoid unused imports such as 'junitx.ddtunit.data.processing.CollectionCreatorAction.CollectionReferenceInfo' | 50 |
These nested if statements could be combined | 222 - 224 |
junitx/ddtunit/data/processing/SubelementCreatorAction.java
Violation | Line |
---|
Avoid unused imports such as 'junitx.ddtunit.data.processing.CollectionCreatorAction.CollectionReferenceInfo' | 51 |
These nested if statements could be combined | 354 - 356 |
junitx/ddtunit/data/processing/parser/ParserImpl.java
Violation | Line |
---|
Avoid unused private fields such as 'XML_LEXICAL_HANDLER_URI'. | 90 |
Avoid empty catch blocks | 303 - 305 |
junitx/ddtunit/util/ClassAnalyser.java
Violation | Line |
---|
These nested if statements could be combined | 727 - 730 |
These nested if statements could be combined | 744 - 747 |
junitx/framework/Assert.java
Violation | Line |
---|
Avoid instantiating Boolean objects; reference Boolean.TRUE or Boolean.FALSE or call Boolean.valueOf() instead. | 305 |
Avoid instantiating Boolean objects; reference Boolean.TRUE or Boolean.FALSE or call Boolean.valueOf() instead. | 305 |
junitx/framework/ThrowableAssert.java
Violation | Line |
---|
These nested if statements could be combined | 125 - 127 |
These nested if statements could be combined | 130 - 132 |