The following document contains the results of PMD 4.2.2.
Violation | Line |
---|---|
Use explicit scoping instead of the default package private level | 46 - 48 |
Use explicit scoping instead of the default package private level | 59 - 70 |
A method should have only one exit point, and that should be the last statement in the method | 74 |
A method should have only one exit point, and that should be the last statement in the method | 84 |
A method should have only one exit point, and that should be the last statement in the method | 92 |
Found 'DD'-anomaly for variable 'config' (lines '102'-'104'). | 102 - 104 |
A method should have only one exit point, and that should be the last statement in the method | 106 |
Found 'DD'-anomaly for variable 'config' (lines '113'-'115'). | 113 - 115 |
A method should have only one exit point, and that should be the last statement in the method | 117 |
Found 'DD'-anomaly for variable 'config' (lines '124'-'126'). | 124 - 126 |
A method should have only one exit point, and that should be the last statement in the method | 128 |
Violation | Line |
---|---|
It is a good practice to call super() in a constructor | 47 - 49 |
Found 'DD'-anomaly for variable 'canonicalPath' (lines '79'-'81'). | 79 - 81 |
Violation | Line |
---|---|
Assigning an Object to null is a code smell. Consider refactoring. | 78 |
Violation | Line |
---|---|
Assigning an Object to null is a code smell. Consider refactoring. | 65 |
Assigning an Object to null is a code smell. Consider refactoring. | 73 |
Avoid using final local variables, turn them into fields | 108 |
Avoid empty catch blocks | 139 - 141 |
Avoid using final local variables, turn them into fields | 153 |
Avoid empty catch blocks | 172 - 174 |
Violation | Line |
---|---|
A method should have only one exit point, and that should be the last statement in the method | 162 |
Violation | Line |
---|---|
These nested if statements could be combined | 69 - 77 |
Assigning an Object to null is a code smell. Consider refactoring. | 72 |
Assigning an Object to null is a code smell. Consider refactoring. | 73 |
Violation | Line |
---|---|
A method should have only one exit point, and that should be the last statement in the method | 80 |
Violation | Line |
---|---|
Assigning an Object to null is a code smell. Consider refactoring. | 92 |
Assigning an Object to null is a code smell. Consider refactoring. | 93 |
Assigning an Object to null is a code smell. Consider refactoring. | 94 |
Violation | Line |
---|---|
Avoid empty catch blocks | 151 - 153 |
Found 'DD'-anomaly for variable 'mBeanOperationInfo' (lines '174'-'177'). | 174 - 177 |
Found 'DU'-anomaly for variable 'i' (lines '175'-'196'). | 175 - 196 |
Found 'DD'-anomaly for variable 'mBeanOperationInfo' (lines '177'-'177'). | 177 |
Found 'DD'-anomaly for variable 'mBeanAttributeInfo' (lines '180'-'183'). | 180 - 183 |
Found 'DU'-anomaly for variable 'j' (lines '181'-'196'). | 181 - 196 |
Found 'DD'-anomaly for variable 'mBeanAttributeInfo' (lines '183'-'183'). | 183 |