Violation | Line |
---|---|
These nested if statements could be combined - details... | 237 |
Avoid instantiating Boolean objects; reference Boolean.TRUE or Boolean.FALSE or call Boolean.valueOf() instead. - details... | 445 |
Violation | Line |
---|---|
Avoid empty catch blocks - details... | 75 |
Avoid empty catch blocks - details... | 113 |
Avoid empty catch blocks - details... | 127 |
Avoid empty catch blocks - details... | 157 |
Avoid empty catch blocks - details... | 281 |
Violation | Line |
---|---|
These nested if statements could be combined - details... | 98 |
Violation | Line |
---|---|
Avoid empty if statements - details... | 272 |
Avoid empty if statements - details... | 274 |
Avoid instantiating Boolean objects; reference Boolean.TRUE or Boolean.FALSE or call Boolean.valueOf() instead. - details... | 316 |
Violation | Line |
---|---|
Avoid instantiating Boolean objects; reference Boolean.TRUE or Boolean.FALSE or call Boolean.valueOf() instead. - details... | 74 |
Violation | Line |
---|---|
Avoid empty catch blocks - details... | 49 |
Violation | Line |
---|---|
Avoid creating BigDecimal with a decimal (float/double) literal. Use a String literal - details... | 106 |
Avoid empty catch blocks - details... | 481 |
Avoid empty catch blocks - details... | 483 |
Avoid creating BigDecimal with a decimal (float/double) literal. Use a String literal - details... | 526 |