The following document contains the results of PMD 3.7.
Violation | Line |
---|---|
Unnecessary final modifier in final class | 35 - 39 |
Unnecessary final modifier in final class | 41 - 61 |
A method should have only one exit point, and that should be the last statement in the method | 45 |
A method should have only one exit point, and that should be the last statement in the method | 49 |
Unnecessary final modifier in final class | 63 - 67 |
Unnecessary final modifier in final class | 69 - 89 |
A method should have only one exit point, and that should be the last statement in the method | 73 |
A method should have only one exit point, and that should be the last statement in the method | 77 |
Unnecessary final modifier in final class | 91 - 93 |
Violation | Line |
---|---|
A method should have only one exit point, and that should be the last statement in the method | 39 |
A method should have only one exit point, and that should be the last statement in the method | 42 |
Violation | Line |
---|---|
Use explicit scoping instead of the default package private level | 17 - 19 |
A method should have only one exit point, and that should be the last statement in the method | 28 |
A method should have only one exit point, and that should be the last statement in the method | 30 |
A method should have only one exit point, and that should be the last statement in the method | 47 |
Unnecessary final modifier in final class | 54 - 85 |
Avoid assigments in operands | 69 - 72 |
Unnecessary final modifier in final class | 87 - 111 |
A method should have only one exit point, and that should be the last statement in the method | 93 |
A method should have only one exit point, and that should be the last statement in the method | 118 |
A method should have only one exit point, and that should be the last statement in the method | 120 |
A method should have only one exit point, and that should be the last statement in the method | 142 |
Avoid assigments in operands | 159 - 162 |
Unnecessary final modifier in final class | 185 - 209 |
A method should have only one exit point, and that should be the last statement in the method | 191 |
Violation | Line |
---|---|
Use explicit scoping instead of the default package private level | 9 |
Violation | Line |
---|---|
Use bitwise inversion to invert boolean values | 41 |
Avoid empty catch blocks | 56 - 57 |
A method should have only one exit point, and that should be the last statement in the method | 143 - 144 |
A method should have only one exit point, and that should be the last statement in the method | 146 - 147 |
A method should have only one exit point, and that should be the last statement in the method | 153 |
A method should have only one exit point, and that should be the last statement in the method | 155 |
A method should have only one exit point, and that should be the last statement in the method | 158 |
A method should have only one exit point, and that should be the last statement in the method | 160 |
An empty statement (semicolon) not part of a loop | 162 |
A method should have only one exit point, and that should be the last statement in the method | 164 - 165 |
A method should have only one exit point, and that should be the last statement in the method | 169 |
A method should have only one exit point, and that should be the last statement in the method | 171 |
A method should have only one exit point, and that should be the last statement in the method | 178 |
A method should have only one exit point, and that should be the last statement in the method | 190 - 191 |
A method should have only one exit point, and that should be the last statement in the method | 193 - 194 |
A method should have only one exit point, and that should be the last statement in the method | 199 |
A method should have only one exit point, and that should be the last statement in the method | 204 - 205 |
A method should have only one exit point, and that should be the last statement in the method | 207 - 208 |
A method should have only one exit point, and that should be the last statement in the method | 213 - 214 |
A method should have only one exit point, and that should be the last statement in the method | 216 - 217 |
An empty statement (semicolon) not part of a loop | 219 |
A method should have only one exit point, and that should be the last statement in the method | 223 - 224 |
A method should have only one exit point, and that should be the last statement in the method | 226 |
A method should have only one exit point, and that should be the last statement in the method | 229 |
A method should have only one exit point, and that should be the last statement in the method | 231 - 232 |
A method should have only one exit point, and that should be the last statement in the method | 233 |
A method should have only one exit point, and that should be the last statement in the method | 238 |
A method should have only one exit point, and that should be the last statement in the method | 240 |
A method should have only one exit point, and that should be the last statement in the method | 247 |
Violation | Line |
---|---|
A method should have only one exit point, and that should be the last statement in the method | 33 |
A method should have only one exit point, and that should be the last statement in the method | 36 |
A method should have only one exit point, and that should be the last statement in the method | 61 |
A method should have only one exit point, and that should be the last statement in the method | 64 |
Violation | Line |
---|---|
These nested if statements could be combined | 71 - 77 |
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 |
A method should have only one exit point, and that should be the last statement in the method | 97 - 98 |
A method should have only one exit point, and that should be the last statement in the method | 114 |
Avoid assigments in operands | 116 - 119 |
Avoid assigments in operands | 127 - 129 |