The following document contains the results of PMD 4.2.2.
Violation | Line |
---|---|
It is a good practice to call super() in a constructor | 68 - 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 | 100 |
A method should have only one exit point, and that should be the last statement in the method | 117 |
Found 'UR'-anomaly for variable 'index' (lines '130'-'130'). | 130 |
Found 'UR'-anomaly for variable 'sextets' (lines '130'-'130'). | 130 |
Found 'UR'-anomaly for variable 'n' (lines '130'-'130'). | 130 |
A method should have only one exit point, and that should be the last statement in the method | 144 |
Found 'DU'-anomaly for variable 'data' (lines '148'-'226'). | 148 - 226 |
Found 'DD'-anomaly for variable 'data' (lines '148'-'187'). | 148 - 187 |
Found 'DD'-anomaly for variable 'sextets' (lines '149'-'188'). | 149 - 188 |
A method should have only one exit point, and that should be the last statement in the method | 164 |
A method should have only one exit point, and that should be the last statement in the method | 180 |
Found 'DD'-anomaly for variable 'sextets' (lines '191'-'188'). | 191 - 188 |
Found 'DU'-anomaly for variable 'sextets' (lines '191'-'226'). | 191 - 226 |
A method should have only one exit point, and that should be the last statement in the method | 217 |
Violation | Line |
---|---|
Use explicit scoping instead of the default package private level | 48 - 53 |
Violation | Line |
---|---|
Use explicit scoping instead of the default package private level | 31 |
Avoid using final local variables, turn them into fields | 40 |
Avoid assignments in operands | 42 |
Found 'DU'-anomaly for variable 'inputLength' (lines '42'-'45'). | 42 - 45 |
Avoid using final local variables, turn them into fields | 70 |
Violation | Line |
---|---|
Found 'DD'-anomaly for variable 'b' (lines '52'-'53'). | 52 - 53 |
Avoid assignments in operands | 53 |
Found 'DU'-anomaly for variable 'b' (lines '53'-'64'). | 53 - 64 |
Found 'DD'-anomaly for variable 'b' (lines '81'-'82'). | 81 - 82 |
Avoid assignments in operands | 82 |
Found 'DU'-anomaly for variable 'b' (lines '82'-'93'). | 82 - 93 |
Found 'DU'-anomaly for variable 'previousEnd' (lines '150'-'183'). | 150 - 183 |
Found 'DU'-anomaly for variable 'previousWasEncoded' (lines '151'-'183'). | 151 - 183 |
Found 'DD'-anomaly for variable 'previousWasEncoded' (lines '151'-'181'). | 151 - 181 |
Found 'DU'-anomaly for variable 'sb' (lines '153'-'183'). | 153 - 183 |
A method should have only one exit point, and that should be the last statement in the method | 160 |
Found 'DU'-anomaly for variable 'previousEnd' (lines '180'-'183'). | 180 - 183 |
Found 'DU'-anomaly for variable 'previousWasEncoded' (lines '181'-'183'). | 181 - 183 |
Found 'DD'-anomaly for variable 'previousWasEncoded' (lines '181'-'181'). | 181 |
A method should have only one exit point, and that should be the last statement in the method | 189 |
A method should have only one exit point, and that should be the last statement in the method | 193 |
Found 'DU'-anomaly for variable 'encoding' (lines '196'-'251'). | 196 - 251 |
Found 'DU'-anomaly for variable 'encodedText' (lines '197'-'251'). | 197 - 251 |
A method should have only one exit point, and that should be the last statement in the method | 206 |
A method should have only one exit point, and that should be the last statement in the method | 214 |
A method should have only one exit point, and that should be the last statement in the method | 222 |
A method should have only one exit point, and that should be the last statement in the method | 227 |
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 | 235 |
A method should have only one exit point, and that should be the last statement in the method | 243 |
Violation | Line |
---|---|
A method should have only one exit point, and that should be the last statement in the method | 111 |
A method should have only one exit point, and that should be the last statement in the method | 113 |
A method should have only one exit point, and that should be the last statement in the method | 135 |
A method should have only one exit point, and that should be the last statement in the method | 157 |
A method should have only one exit point, and that should be the last statement in the method | 180 |
Found 'DD'-anomaly for variable 'nonWhiteSpaceCount' (lines '205'-'210'). | 205 - 210 |
Found 'DD'-anomaly for variable 'nonWhiteSpaceCount' (lines '205'-'212'). | 205 - 212 |
Found 'DU'-anomaly for variable 'nonWhiteSpaceCount' (lines '205'-'229'). | 205 - 229 |
Found 'DD'-anomaly for variable 'nonWhiteSpaceCount' (lines '210'-'210'). | 210 |
Found 'DU'-anomaly for variable 'nonWhiteSpaceCount' (lines '210'-'229'). | 210 - 229 |
Found 'DD'-anomaly for variable 'nonWhiteSpaceCount' (lines '210'-'212'). | 210 - 212 |
A method should have only one exit point, and that should be the last statement in the method | 218 |
A method should have only one exit point, and that should be the last statement in the method | 223 |
A method should have only one exit point, and that should be the last statement in the method | 326 |
Avoid using final local variables, turn them into fields | 345 |
Found 'DU'-anomaly for variable 'qChars' (lines '385'-'405'). | 385 - 405 |
Avoid using final local variables, turn them into fields | 390 |
Avoid using final local variables, turn them into fields | 422 |
A method should have only one exit point, and that should be the last statement in the method | 424 |
A method should have only one exit point, and that should be the last statement in the method | 429 |
Found 'DD'-anomaly for variable 'containsAText' (lines '438'-'444'). | 438 - 444 |
Found 'DU'-anomaly for variable 'containsAText' (lines '438'-'451'). | 438 - 451 |
Avoid using final local variables, turn them into fields | 440 |
Found 'DD'-anomaly for variable 'containsAText' (lines '444'-'444'). | 444 |
Found 'DU'-anomaly for variable 'containsAText' (lines '444'-'451'). | 444 - 451 |
A method should have only one exit point, and that should be the last statement in the method | 446 |
Found 'DU'-anomaly for variable 'prev' (lines '459'-'480'). | 459 - 480 |
Found 'DD'-anomaly for variable 'prev' (lines '459'-'476'). | 459 - 476 |
Avoid using final local variables, turn them into fields | 461 |
A method should have only one exit point, and that should be the last statement in the method | 463 |
A method should have only one exit point, and that should be the last statement in the method | 470 |
A method should have only one exit point, and that should be the last statement in the method | 473 |
Found 'DU'-anomaly for variable 'prev' (lines '476'-'480'). | 476 - 480 |
Found 'DD'-anomaly for variable 'prev' (lines '476'-'476'). | 476 |
A method should have only one exit point, and that should be the last statement in the method | 502 |
A method should have only one exit point, and that should be the last statement in the method | 528 |
Found 'DU'-anomaly for variable 'qChars' (lines '544'-'561'). | 544 - 561 |
Found 'DD'-anomaly for variable 'count' (lines '547'-'552'). | 547 - 552 |
Found 'DD'-anomaly for variable 'count' (lines '547'-'556'). | 547 - 556 |
Found 'DD'-anomaly for variable 'count' (lines '552'-'552'). | 552 |
Found 'DD'-anomaly for variable 'count' (lines '552'-'556'). | 552 - 556 |
Found 'DD'-anomaly for variable 'count' (lines '556'-'552'). | 556 - 552 |
Found 'DD'-anomaly for variable 'count' (lines '556'-'556'). | 556 |
Found 'DU'-anomaly for variable 'ascii' (lines '573'-'585'). | 573 - 585 |
Found 'DD'-anomaly for variable 'ascii' (lines '573'-'581'). | 573 - 581 |
Avoid using final local variables, turn them into fields | 574 |
A method should have only one exit point, and that should be the last statement in the method | 578 |
Found 'DU'-anomaly for variable 'ascii' (lines '581'-'585'). | 581 - 585 |
Found 'DD'-anomaly for variable 'ascii' (lines '581'-'581'). | 581 |
A method should have only one exit point, and that should be the last statement in the method | 589 |
Found 'DU'-anomaly for variable 'qChars' (lines '591'-'604'). | 591 - 604 |
Found 'DD'-anomaly for variable 'qEncoded' (lines '594'-'598'). | 594 - 598 |
Found 'DD'-anomaly for variable 'qEncoded' (lines '598'-'598'). | 598 |
Violation | Line |
---|---|
Assigning an Object to null is a code smell. Consider refactoring. | 54 |
Use explicit scoping instead of the default package private level | 61 - 67 |
Use explicit scoping instead of the default package private level | 69 - 73 |
Use explicit scoping instead of the default package private level | 75 - 78 |
Avoid assignments in operands | 83 |
Found 'DU'-anomaly for variable 'inputLength' (lines '83'-'87'). | 83 - 87 |
Use explicit scoping instead of the default package private level | 198 - 205 |
Violation | Line |
---|---|
Use explicit scoping instead of the default package private level | 35 |
Use explicit scoping instead of the default package private level | 36 |
It is a good practice to call super() in a constructor | 40 - 42 |
A method should have only one exit point, and that should be the last statement in the method | 62 |
A method should have only one exit point, and that should be the last statement in the method | 66 |
A method should have only one exit point, and that should be the last statement in the method | 85 |
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 | 102 |
Found 'DU'-anomaly for variable 'msdChar' (lines '119'-'206'). | 119 - 206 |
Found 'DD'-anomaly for variable 'msdChar' (lines '119'-'144'). | 119 - 144 |
Found 'DU'-anomaly for variable 'msdChar' (lines '144'-'206'). | 144 - 206 |
A method should have only one exit point, and that should be the last statement in the method | 215 |
A method should have only one exit point, and that should be the last statement in the method | 217 |
Violation | Line |
---|---|
Found 'DD'-anomaly for variable 'size' (lines '88'-'91'). | 88 - 91 |
Found 'DD'-anomaly for variable 'size' (lines '88'-'93'). | 88 - 93 |
Found 'DD'-anomaly for variable 'tmp' (lines '117'-'121'). | 117 - 121 |
Found 'DD'-anomaly for variable 'tmp' (lines '121'-'121'). | 121 |
Violation | Line |
---|---|
Found 'DD'-anomaly for variable 'name' (lines '96'-'99'). | 96 - 99 |
Found 'DD'-anomaly for variable 'value' (lines '97'-'104'). | 97 - 104 |
Found 'DU'-anomaly for variable 'value' (lines '97'-'118'). | 97 - 118 |
Found 'DD'-anomaly for variable 'type' (lines '126'-'133'). | 126 - 133 |
Found 'DD'-anomaly for variable 'type' (lines '126'-'143'). | 126 - 143 |
Found 'DU'-anomaly for variable 'type' (lines '126'-'181'). | 126 - 181 |
Found 'DD'-anomaly for variable 'subtype' (lines '127'-'134'). | 127 - 134 |
Found 'DD'-anomaly for variable 'subtype' (lines '127'-'144'). | 127 - 144 |
Found 'DU'-anomaly for variable 'subtype' (lines '127'-'181'). | 127 - 181 |
Found 'DD'-anomaly for variable 'valid' (lines '131'-'137'). | 131 - 137 |
Found 'DD'-anomaly for variable 'main' (lines '136'-'142'). | 136 - 142 |
Assigning an Object to null is a code smell. Consider refactoring. | 142 |
Assigning an Object to null is a code smell. Consider refactoring. | 143 |
Found 'DU'-anomaly for variable 'type' (lines '143'-'181'). | 143 - 181 |
Assigning an Object to null is a code smell. Consider refactoring. | 144 |
Found 'DU'-anomaly for variable 'subtype' (lines '144'-'181'). | 144 - 181 |
Assigning an Object to null is a code smell. Consider refactoring. | 163 |
Violation | Line |
---|---|
Assigning an Object to null is a code smell. Consider refactoring. | 82 |
Assigning an Object to null is a code smell. Consider refactoring. | 84 |
Assigning an Object to null is a code smell. Consider refactoring. | 86 |
Assigning an Object to null is a code smell. Consider refactoring. | 88 |
Assigning an Object to null is a code smell. Consider refactoring. | 89 |
Assigning an Object to null is a code smell. Consider refactoring. | 90 |
Assigning an Object to null is a code smell. Consider refactoring. | 91 |
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. | 95 |
Assigning an Object to null is a code smell. Consider refactoring. | 97 |
Assigning an Object to null is a code smell. Consider refactoring. | 98 |
Assigning an Object to null is a code smell. Consider refactoring. | 100 |
Assigning an Object to null is a code smell. Consider refactoring. | 101 |
Assigning an Object to null is a code smell. Consider refactoring. | 103 |
Found 'DD'-anomaly for variable 'name' (lines '109'-'111'). | 109 - 111 |
Found 'DU'-anomaly for variable 'value' (lines '110'-'129'). | 110 - 129 |
Avoid using final local variables, turn them into fields | 141 |
Avoid using final local variables, turn them into fields | 142 |
Avoid using final local variables, turn them into fields | 156 |
Avoid using final local variables, turn them into fields | 169 - 170 |
Avoid using final local variables, turn them into fields | 179 - 180 |
Avoid using final local variables, turn them into fields | 189 - 190 |
Avoid using final local variables, turn them into fields | 199 |
Avoid using final local variables, turn them into fields | 211 |
Avoid using final local variables, turn them into fields | 212 |
Avoid using final local variables, turn them into fields | 236 |
Avoid using final local variables, turn them into fields | 237 |
Avoid using final local variables, turn them into fields | 240 |
Avoid using final local variables, turn them into fields | 244 |
Violation | Line |
---|---|
Avoid using final local variables, turn them into fields | 155 |
Avoid using final local variables, turn them into fields | 160 |
Avoid using final local variables, turn them into fields | 164 |
Violation | Line |
---|---|
Use explicit scoping instead of the default package private level | 42 - 44 |
Violation | Line |
---|---|
It is a good practice to call super() in a constructor | 48 - 54 |
Found 'DD'-anomaly for variable 'groupDetected' (lines '78'-'81'). | 78 - 81 |
Avoid using final local variables, turn them into fields | 87 - 88 |
A method should have only one exit point, and that should be the last statement in the method | 89 |
Found 'DU'-anomaly for variable 'reader' (lines '129'-'147'). | 129 - 147 |
Violation | Line |
---|---|
A method should have only one exit point, and that should be the last statement in the method | 68 |
A method should have only one exit point, and that should be the last statement in the method | 70 |
Found 'DD'-anomaly for variable 'name' (lines '72'-'77'). | 72 - 77 |
Found 'DU'-anomaly for variable 'name' (lines '72'-'85'). | 72 - 85 |
A method should have only one exit point, and that should be the last statement in the method | 75 |
Found 'DU'-anomaly for variable 'results' (lines '88'-'98'). | 88 - 98 |
A method should have only one exit point, and that should be the last statement in the method | 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 'name' (lines '119'-'126'). | 119 - 126 |
Found 'DU'-anomaly for variable 'name' (lines '119'-'131'). | 119 - 131 |
Found 'DD'-anomaly for variable 'route' (lines '135'-'138'). | 135 - 138 |
Found 'DU'-anomaly for variable 'route' (lines '135'-'150'). | 135 - 150 |
Found 'DU'-anomaly for variable 'route' (lines '138'-'150'). | 138 - 150 |
Avoid empty if statements | 140 - 142 |
Found 'DU'-anomaly for variable 'results' (lines '153'-'163'). | 153 - 163 |
Violation | Line |
---|---|
It is a good practice to call super() in a constructor | 45 - 50 |
Violation | Line |
---|---|
It is a good practice to call super() in a constructor | 65 - 73 |
Found 'DU'-anomaly for variable 'first' (lines '113'-'128'). | 113 - 128 |
Found 'DU'-anomaly for variable 'first' (lines '116'-'128'). | 116 - 128 |
Found 'DU'-anomaly for variable 'first' (lines '137'-'152'). | 137 - 152 |
Found 'DU'-anomaly for variable 'first' (lines '140'-'152'). | 140 - 152 |
Violation | Line |
---|---|
It is a good practice to call super() in a constructor | 100 - 109 |
Assigning an Object to null is a code smell. Consider refactoring. | 105 |
Assigning an Object to null is a code smell. Consider refactoring. | 108 |
A method should have only one exit point, and that should be the last statement in the method | 177 |
A method should have only one exit point, and that should be the last statement in the method | 266 |
A method should have only one exit point, and that should be the last statement in the method | 268 |
A method should have only one exit point, and that should be the last statement in the method | 282 |
Violation | Line |
---|---|
It is a good practice to call super() in a constructor | 44 - 50 |
Violation | Line |
---|---|
Each class should declare at least one constructor | 23 - 28 |
Violation | Line |
---|---|
Use explicit scoping instead of the default package private level | 73 - 78 |
Violation | Line |
---|---|
A method should have only one exit point, and that should be the last statement in the method | 243 |
A method should have only one exit point, and that should be the last statement in the method | 247 |
A method should have only one exit point, and that should be the last statement in the method | 259 |
A method should have only one exit point, and that should be the last statement in the method | 263 - 264 |
A method should have only one exit point, and that should be the last statement in the method | 270 |
Avoid using final local variables, turn them into fields | 299 |
Avoid using final local variables, turn them into fields | 308 |
Use explicit scoping instead of the default package private level | 320 - 325 |
Violation | Line |
---|---|
A method should have only one exit point, and that should be the last statement in the method | 54 |
Use explicit scoping instead of the default package private level | 59 - 64 |
Violation | Line |
---|---|
A method should have only one exit point, and that should be the last statement in the method | 186 |
A method should have only one exit point, and that should be the last statement in the method | 188 |
A method should have only one exit point, and that should be the last statement in the method | 206 |
Avoid using final local variables, turn them into fields | 230 |
Avoid using final local variables, turn them into fields | 231 |
Avoid using final local variables, turn them into fields | 240 |
Use explicit scoping instead of the default package private level | 252 - 257 |
Violation | Line |
---|---|
A method should have only one exit point, and that should be the last statement in the method | 54 |
A method should have only one exit point, and that should be the last statement in the method | 56 |
A method should have only one exit point, and that should be the last statement in the method | 58 |
Avoid using final local variables, turn them into fields | 120 |
Found 'DD'-anomaly for variable 'result' (lines '121'-'122'). | 121 - 122 |
A method should have only one exit point, and that should be the last statement in the method | 136 |
A method should have only one exit point, and that should be the last statement in the method | 138 |
A method should have only one exit point, and that should be the last statement in the method | 140 |
Avoid using final local variables, turn them into fields | 141 |
A method should have only one exit point, and that should be the last statement in the method | 144 |
A method should have only one exit point, and that should be the last statement in the method | 146 |
A method should have only one exit point, and that should be the last statement in the method | 148 |
A method should have only one exit point, and that should be the last statement in the method | 150 |
A method should have only one exit point, and that should be the last statement in the method | 152 |
A method should have only one exit point, and that should be the last statement in the method | 154 |
A method should have only one exit point, and that should be the last statement in the method | 156 |
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 |
Violation | Line |
---|---|
Use explicit scoping instead of the default package private level | 83 - 88 |
Violation | Line |
---|---|
It is a good practice to call super() in a constructor | 24 - 51 |
Avoid using final local variables, turn them into fields | 31 |
Avoid using final local variables, turn them into fields | 35 |
Avoid using final local variables, turn them into fields | 39 |
Avoid using final local variables, turn them into fields | 43 |
Violation | Line |
---|---|
Avoid using final local variables, turn them into fields | 42 |
A method should have only one exit point, and that should be the last statement in the method | 44 |
Avoid using final local variables, turn them into fields | 50 |
Violation | Line |
---|---|
A method should have only one exit point, and that should be the last statement in the method | 82 - 83 |
A method should have only one exit point, and that should be the last statement in the method | 145 - 146 |
Avoid using final local variables, turn them into fields | 559 |
A method should have only one exit point, and that should be the last statement in the method | 587 |
A method should have only one exit point, and that should be the last statement in the method | 591 |
A method should have only one exit point, and that should be the last statement in the method | 600 |
Violation | Line |
---|---|
Use explicit scoping instead of the default package private level | 78 - 83 |
Violation | Line |
---|---|
Use explicit scoping instead of the default package private level | 74 - 79 |
Violation | Line |
---|---|
Use explicit scoping instead of the default package private level | 52 - 57 |
Violation | Line |
---|---|
A method should have only one exit point, and that should be the last statement in the method | 96 |
A method should have only one exit point, and that should be the last statement in the method | 115 |
Found 'DD'-anomaly for variable 'noRead' (lines '117'-'119'). | 117 - 119 |
Found 'DU'-anomaly for variable 'noRead' (lines '117'-'125'). | 117 - 125 |
A method should have only one exit point, and that should be the last statement in the method | 121 |
A method should have only one exit point, and that should be the last statement in the method | 130 |
A method should have only one exit point, and that should be the last statement in the method | 133 |
Found 'DD'-anomaly for variable 'noRead' (lines '135'-'137'). | 135 - 137 |
Found 'DU'-anomaly for variable 'noRead' (lines '135'-'149'). | 135 - 149 |
A method should have only one exit point, and that should be the last statement in the method | 139 |
A method should have only one exit point, and that should be the last statement in the method | 154 |
A method should have only one exit point, and that should be the last statement in the method | 157 |
A method should have only one exit point, and that should be the last statement in the method | 174 |
Found 'DU'-anomaly for variable 'total' (lines '176'-'208'). | 176 - 208 |
Found 'DD'-anomaly for variable 'bytesRead' (lines '178'-'181'). | 178 - 181 |
Found 'DU'-anomaly for variable 'bytesRead' (lines '178'-'208'). | 178 - 208 |
Found 'DU'-anomaly for variable 'found' (lines '189'-'208'). | 189 - 208 |
A method should have only one exit point, and that should be the last statement in the method | 204 |
A method should have only one exit point, and that should be the last statement in the method | 226 |
Found 'DD'-anomaly for variable 'shiftTable' (lines '235'-'235'). | 235 |
Found 'DU'-anomaly for variable 'shiftTable' (lines '235'-'260'). | 235 - 260 |
Found 'DD'-anomaly for variable 'match' (lines '241'-'244'). | 241 - 244 |
A method should have only one exit point, and that should be the last statement in the method | 249 |
A method should have only one exit point, and that should be the last statement in the method | 280 |
Violation | Line |
---|---|
A method should have only one exit point, and that should be the last statement in the method | 86 |
Violation | Line |
---|---|
Assigning an Object to null is a code smell. Consider refactoring. | 47 |
Found 'DD'-anomaly for variable 'total' (lines '87'-'91'). | 87 - 91 |
Avoid assignments in operands | 89 |
Found 'DU'-anomaly for variable 'total' (lines '91'-'104'). | 91 - 104 |
Found 'DD'-anomaly for variable 'total' (lines '91'-'91'). | 91 |
A method should have only one exit point, and that should be the last statement in the method | 100 |
Violation | Line |
---|---|
A method should have only one exit point, and that should be the last statement in the method | 101 |
A method should have only one exit point, and that should be the last statement in the method | 105 |
A method should have only one exit point, and that should be the last statement in the method | 109 |
A method should have only one exit point, and that should be the last statement in the method | 121 |
A method should have only one exit point, and that should be the last statement in the method | 125 |
A method should have only one exit point, and that should be the last statement in the method | 129 |
A method should have only one exit point, and that should be the last statement in the method | 141 |
A method should have only one exit point, and that should be the last statement in the method | 145 |
Found 'DD'-anomaly for variable 'bytesRead' (lines '150'-'153'). | 150 - 153 |
Found 'DD'-anomaly for variable 'bytesRead' (lines '153'-'156'). | 153 - 156 |
Found 'DD'-anomaly for variable 'bytesRead' (lines '153'-'153'). | 153 |
A method should have only one exit point, and that should be the last statement in the method | 176 |
A method should have only one exit point, and that should be the last statement in the method | 192 |
These nested if statements could be combined | 231 - 234 |
These nested if statements could be combined | 237 - 240 |
Found 'DU'-anomaly for variable 'checkForLastPart' (lines '248'-'280'). | 248 - 280 |
These nested if statements could be combined | 254 - 259 |
Found 'DU'-anomaly for variable 'checkForLastPart' (lines '257'-'280'). | 257 - 280 |
Avoid using final local variables, turn them into fields | 292 |
Violation | Line |
---|---|
Avoid using final local variables, turn them into fields | 77 |
Avoid using final local variables, turn them into fields | 85 |
Violation | Line |
---|---|
It is a good practice to call super() in a constructor | 33 - 34 |
Violation | Line |
---|---|
A method should have only one exit point, and that should be the last statement in the method | 57 |
A method should have only one exit point, and that should be the last statement in the method | 60 |
Violation | Line |
---|---|
A method should have only one exit point, and that should be the last statement in the method | 288 |
A method should have only one exit point, and that should be the last statement in the method | 296 |
A method should have only one exit point, and that should be the last statement in the method | 304 |
Violation | Line |
---|---|
It is a good practice to call super() in a constructor | 30 - 31 |
Violation | Line |
---|---|
Found 'UR'-anomaly for variable 'body' (lines '146'-'147'). | 146 - 147 |
A method should have only one exit point, and that should be the last statement in the method | 148 |
Assigning an Object to null is a code smell. Consider refactoring. | 151 |
Found 'DD'-anomaly for variable 'parameters' (lines '236'-'239'). | 236 - 239 |
A method should have only one exit point, and that should be the last statement in the method | 343 |
A method should have only one exit point, and that should be the last statement in the method | 443 |
Use explicit scoping instead of the default package private level | 530 - 535 |
Use explicit scoping instead of the default package private level | 547 - 555 |
A method should have only one exit point, and that should be the last statement in the method | 550 |
Violation | Line |
---|---|
Avoid using final local variables, turn them into fields | 77 |
A method should have only one exit point, and that should be the last statement in the method | 130 |
Avoid using final local variables, turn them into fields | 142 |
Avoid using final local variables, turn them into fields | 143 |
Avoid using final local variables, turn them into fields | 144 |
Avoid using final local variables, turn them into fields | 170 |
A method should have only one exit point, and that should be the last statement in the method | 173 |
Avoid using final local variables, turn them into fields | 197 |
Found 'DD'-anomaly for variable 'index' (lines '208'-'209'). | 208 - 209 |
Found 'DU'-anomaly for variable 'index' (lines '208'-'220'). | 208 - 220 |
Found 'DU'-anomaly for variable 'index' (lines '209'-'220'). | 209 - 220 |
Found 'DD'-anomaly for variable 'index' (lines '209'-'209'). | 209 |
Violation | Line |
---|---|
It is a good practice to call super() in a constructor | 63 - 64 |
It is a good practice to call super() in a constructor | 135 - 145 |
A method should have only one exit point, and that should be the last statement in the method | 170 |
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 | 233 |
A method should have only one exit point, and that should be the last statement in the method | 533 |
A method should have only one exit point, and that should be the last statement in the method | 551 |
A method should have only one exit point, and that should be the last statement in the method | 579 |
Violation | Line |
---|---|
Avoid using final local variables, turn them into fields | 121 |
Avoid using final local variables, turn them into fields | 122 |
Avoid using final local variables, turn them into fields | 123 |
Avoid using final local variables, turn them into fields | 134 |
Avoid using final local variables, turn them into fields | 136 |
Avoid using final local variables, turn them into fields | 138 |
Avoid assignments in operands | 213 |
Found 'DU'-anomaly for variable 'b' (lines '213'-'218'). | 213 - 218 |
Violation | Line |
---|---|
Avoid using final local variables, turn them into fields | 93 |
Avoid using final local variables, turn them into fields | 99 |
A method should have only one exit point, and that should be the last statement in the method | 174 |
A method should have only one exit point, and that should be the last statement in the method | 176 |
Violation | Line |
---|---|
Use explicit scoping instead of the default package private level | 242 - 244 |
Use explicit scoping instead of the default package private level | 246 - 249 |
Assigning an Object to null is a code smell. Consider refactoring. | 248 |
Use explicit scoping instead of the default package private level | 275 - 277 |
Use explicit scoping instead of the default package private level | 279 - 282 |
Assigning an Object to null is a code smell. Consider refactoring. | 281 |
Violation | Line |
---|---|
Assigning an Object to null is a code smell. Consider refactoring. | 90 |
Violation | Line |
---|---|
It is a good practice to call super() in a constructor | 37 - 39 |
Assigning an Object to null is a code smell. Consider refactoring. | 71 |
Violation | Line |
---|---|
It is a good practice to call super() in a constructor | 41 - 44 |
Assigning an Object to null is a code smell. Consider refactoring. | 81 |
Violation | Line |
---|---|
It is a good practice to call super() in a constructor | 40 - 43 |
Found 'DU'-anomaly for variable 'buffer' (lines '63'-'74'). | 63 - 74 |
Violation | Line |
---|---|
It is a good practice to call super() in a constructor | 33 - 34 |
Violation | Line |
---|---|
Avoid using final local variables, turn them into fields | 108 |
Found 'DU'-anomaly for variable 'maxLineLen' (lines '129'-'172'). | 129 - 172 |
Found 'DU'-anomaly for variable 'instream' (lines '130'-'172'). | 130 - 172 |
Found 'DU'-anomaly for variable 'maxHeaderLimit' (lines '175'-'218'). | 175 - 218 |
A method should have only one exit point, and that should be the last statement in the method | 178 |
Found 'DD'-anomaly for variable 'valid' (lines '197'-'202'). | 197 - 202 |
Found 'DD'-anomaly for variable 'valid' (lines '197'-'207'). | 197 - 207 |
Avoid using final local variables, turn them into fields | 284 |
A method should have only one exit point, and that should be the last statement in the method | 293 |
Avoid using final local variables, turn them into fields | 332 |
Violation | Line |
---|---|
A method should have only one exit point, and that should be the last statement in the method | 56 |
A method should have only one exit point, and that should be the last statement in the method | 57 |
A method should have only one exit point, and that should be the last statement in the method | 60 |
Violation | Line |
---|---|
A method should have only one exit point, and that should be the last statement in the method | 106 |
Found 'DU'-anomaly for variable 'mimeType' (lines '133'-'199'). | 133 - 199 |
A method should have only one exit point, and that should be the last statement in the method | 142 |
A method should have only one exit point, and that should be the last statement in the method | 165 |
A method should have only one exit point, and that should be the last statement in the method | 177 |
Assigning an Object to null is a code smell. Consider refactoring. | 229 |
Avoid empty while statements | 241 - 242 |
A method should have only one exit point, and that should be the last statement in the method | 261 |
A method should have only one exit point, and that should be the last statement in the method | 281 |
A method should have only one exit point, and that should be the last statement in the method | 302 |
Violation | Line |
---|---|
Found 'DD'-anomaly for variable 'state' (lines '144'-'91'). | 144 - 91 |
Found 'DU'-anomaly for variable 'state' (lines '144'-'146'). | 144 - 146 |
Violation | Line |
---|---|
Found 'DD'-anomaly for variable 'lineSource' (lines '153'-'156'). | 153 - 156 |
Found 'DU'-anomaly for variable 'lineSource' (lines '153'-'189'). | 153 - 189 |
Found 'DU'-anomaly for variable 'lineSource' (lines '156'-'189'). | 156 - 189 |
Found 'DD'-anomaly for variable 'dataStream' (lines '282'-'284'). | 282 - 284 |
Found 'DD'-anomaly for variable 'dataStream' (lines '282'-'286'). | 282 - 286 |
Avoid using final local variables, turn them into fields | 309 |
Avoid using final local variables, turn them into fields | 310 |
Avoid using final local variables, turn them into fields | 311 |
Avoid using final local variables, turn them into fields | 317 |
A method should have only one exit point, and that should be the last statement in the method | 363 |
Assigning an Object to null is a code smell. Consider refactoring. | 367 |
Violation | Line |
---|---|
It is a good practice to call super() in a constructor | 74 - 85 |
It is a good practice to call super() in a constructor | 106 - 120 |
Assigning an Object to null is a code smell. Consider refactoring. | 157 |
Violation | Line |
---|---|
Use of modifier volatile is not recommended. | 46 |
Use explicit scoping instead of the default package private level | 96 - 99 |
Assigning an Object to null is a code smell. Consider refactoring. | 97 |
Violation | Line |
---|---|
Avoid unnecessary constructors - the compiler will generate these for you | 43 - 44 |
It is a good practice to call super() in a constructor | 43 - 44 |
Use explicit scoping instead of the default package private level | 52 |
Assigning an Object to null is a code smell. Consider refactoring. | 83 |
Violation | Line |
---|---|
It is a good practice to call super() in a constructor | 47 - 48 |
Violation | Line |
---|---|
It is a good practice to call super() in a constructor | 90 - 101 |
It is a good practice to call super() in a constructor | 115 - 118 |
Assigning an Object to null is a code smell. Consider refactoring. | 161 |
Violation | Line |
---|---|
It is a good practice to call super() in a constructor | 67 - 75 |
It is a good practice to call super() in a constructor | 87 - 90 |
Avoid using final local variables, turn them into fields | 88 |
A method should have only one exit point, and that should be the last statement in the method | 122 - 123 |
Assigning an Object to null is a code smell. Consider refactoring. | 145 |
Assigning an Object to null is a code smell. Consider refactoring. | 147 |
Violation | Line |
---|---|
A method should have only one exit point, and that should be the last statement in the method | 67 |
A method should have only one exit point, and that should be the last statement in the method | 136 |
A method should have only one exit point, and that should be the last statement in the method | 140 |
Violation | Line |
---|---|
Avoid empty catch blocks | 1024 - 1025 |
Avoid empty catch blocks | 1025 - 1026 |
Avoid empty catch blocks | 1030 - 1031 |
Avoid empty catch blocks | 1031 - 1032 |
Avoid using final local variables, turn them into fields | 1108 |
A method should have only one exit point, and that should be the last statement in the method | 1111 |
Avoid using final local variables, turn them into fields | 1143 |
A method should have only one exit point, and that should be the last statement in the method | 1146 |
A method should have only one exit point, and that should be the last statement in the method | 1192 |
A method should have only one exit point, and that should be the last statement in the method | 1211 |
Found 'DU'-anomaly for variable 'defaultCharset' (lines '1,217'-'1,234'). | 1217 - 1234 |
A method should have only one exit point, and that should be the last statement in the method | 1223 |
A method should have only one exit point, and that should be the last statement in the method | 1227 |
Violation | Line |
---|---|
A method should have only one exit point, and that should be the last statement in the method | 125 |
Violation | Line |
---|---|
Found 'UR'-anomaly for variable 'IN_NAME' (lines '176'-'176'). | 176 |
Found 'UR'-anomaly for variable 'VALUE_DONE' (lines '176'-'176'). | 176 |
Found 'UR'-anomaly for variable 'ERROR' (lines '176'-'176'). | 176 |
Found 'UR'-anomaly for variable 'READY_FOR_NAME' (lines '176'-'176'). | 176 |
Found 'UR'-anomaly for variable 'IN_QUOTED_VALUE' (lines '176'-'176'). | 176 |
Found 'UR'-anomaly for variable 'READY_FOR_VALUE' (lines '176'-'176'). | 176 |
Found 'UR'-anomaly for variable 'IN_VALUE' (lines '176'-'176'). | 176 |
Assigning an Object to null is a code smell. Consider refactoring. | 188 |
Found 'DU'-anomaly for variable 'paramName' (lines '197'-'343'). | 197 - 343 |
Found 'DU'-anomaly for variable 'paramValue' (lines '198'-'343'). | 198 - 343 |
Avoid using final local variables, turn them into fields | 200 |
Avoid using final local variables, turn them into fields | 201 |
Found 'DU'-anomaly for variable 'IN_NAME' (lines '201'-'343'). | 201 - 343 |
Avoid using final local variables, turn them into fields | 202 |
Found 'DU'-anomaly for variable 'READY_FOR_VALUE' (lines '202'-'343'). | 202 - 343 |
Avoid using final local variables, turn them into fields | 203 |
Avoid using final local variables, turn them into fields | 204 |
Found 'DU'-anomaly for variable 'IN_QUOTED_VALUE' (lines '204'-'343'). | 204 - 343 |
Avoid using final local variables, turn them into fields | 205 |
Found 'DU'-anomaly for variable 'VALUE_DONE' (lines '205'-'343'). | 205 - 343 |
Avoid using final local variables, turn them into fields | 206 |
Found 'DU'-anomaly for variable 'ERROR' (lines '206'-'343'). | 206 - 343 |
Found 'DU'-anomaly for variable 'escaped' (lines '209'-'343'). | 209 - 343 |
Found 'DD'-anomaly for variable 'state' (lines '227'-'233'). | 227 - 233 |
Found 'DD'-anomaly for variable 'state' (lines '227'-'235'). | 227 - 235 |
Found 'DD'-anomaly for variable 'fallThrough' (lines '244'-'256'). | 244 - 256 |
Found 'DD'-anomaly for variable 'state' (lines '251'-'273'). | 251 - 273 |
Found 'DD'-anomaly for variable 'state' (lines '251'-'286'). | 251 - 286 |
Found 'DD'-anomaly for variable 'state' (lines '251'-'294'). | 251 - 294 |
Found 'DD'-anomaly for variable 'state' (lines '255'-'273'). | 255 - 273 |
Found 'DD'-anomaly for variable 'state' (lines '255'-'286'). | 255 - 286 |
Found 'DD'-anomaly for variable 'state' (lines '255'-'294'). | 255 - 294 |
Found 'DD'-anomaly for variable 'fallThrough' (lines '265'-'274'). | 265 - 274 |
Found 'DD'-anomaly for variable 'state' (lines '273'-'286'). | 273 - 286 |
Found 'DD'-anomaly for variable 'state' (lines '273'-'294'). | 273 - 294 |
Found 'DU'-anomaly for variable 'escaped' (lines '309'-'343'). | 309 - 343 |
Use bitwise inversion to invert boolean values | 318 |
Found 'DU'-anomaly for variable 'escaped' (lines '325'-'343'). | 325 - 343 |
Avoid using final local variables, turn them into fields | 431 |
Avoid using final local variables, turn them into fields | 433 |
A method should have only one exit point, and that should be the last statement in the method | 435 |
Found 'DU'-anomaly for variable 'sb' (lines '437'-'457'). | 437 - 457 |
Found 'DU'-anomaly for variable 'lastLineBreak' (lines '439'-'457'). | 439 - 457 |
Found 'DU'-anomaly for variable 'wspIdx' (lines '440'-'457'). | 440 - 457 |
Found 'DU'-anomaly for variable 'lastLineBreak' (lines '452'-'457'). | 452 - 457 |
Found 'DU'-anomaly for variable 'wspIdx' (lines '455'-'457'). | 455 - 457 |
Avoid using final local variables, turn them into fields | 467 |
A method should have only one exit point, and that should be the last statement in the method | 471 |
Avoid using final local variables, turn them into fields | 479 |
Avoid using final local variables, turn them into fields | 497 |
A method should have only one exit point, and that should be the last statement in the method | 501 |
Violation | Line |
---|---|
A method should have only one exit point, and that should be the last statement in the method | 60 |
A method should have only one exit point, and that should be the last statement in the method | 63 |
A method should have only one exit point, and that should be the last statement in the method | 66 |
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 | 87 |
A method should have only one exit point, and that should be the last statement in the method | 90 |
Avoid using final local variables, turn them into fields | 93 |
A method should have only one exit point, and that should be the last statement in the method | 109 |
A method should have only one exit point, and that should be the last statement in the method | 112 - 125 |
Avoid using final local variables, turn them into fields | 121 |
Assigning an Object to null is a code smell. Consider refactoring. | 122 |
Avoid using final local variables, turn them into fields | 128 |
Found 'DU'-anomaly for variable 'values' (lines '128'-'148'). | 128 - 148 |
Found 'DU'-anomaly for variable 'values' (lines '128'-'148'). | 128 - 148 |
Found 'DU'-anomaly for variable 'values' (lines '128'-'148'). | 128 - 148 |
Found 'DU'-anomaly for variable 'values' (lines '128'-'148'). | 128 - 148 |
Found 'DU'-anomaly for variable 'values' (lines '128'-'148'). | 128 - 148 |
A method should have only one exit point, and that should be the last statement in the method | 129 - 140 |
Avoid using final local variables, turn them into fields | 143 - 144 |
Avoid using final local variables, turn them into fields | 157 |
Avoid using final local variables, turn them into fields | 171 |
Avoid using final local variables, turn them into fields | 176 - 177 |
Avoid using final local variables, turn them into fields | 180 |
Avoid using final local variables, turn them into fields | 181 |
Avoid using final local variables, turn them into fields | 250 |