The following document contains the results of PMD 4.2.2.
Violation | Line |
---|---|
Avoid excessively long variable names like csvToObjectExpression | 48 |
Avoid excessively long variable names like objectToCsvExpression | 54 |
Avoid excessively long variable names like formattedPropertyValue | 199 |
Avoid excessively long variable names like csvFieldValidationContext | 202 |
Caught exception is rethrown, original stack trace may be lost | 210 - 214 |
Avoid throwing raw exception types. | 229 |
Avoid if (x != y) ..; else ..; | 254 - 267 |
Avoid throwing raw exception types. | 263 |
Avoid excessively long variable names like csvToObjectExpression | 324 |
Avoid excessively long variable names like objectToCsvExpression | 340 |
Avoid excessively long variable names like newCsvFieldMapping | 359 |
Avoid instantiating String objects; this is usually unnecessary. | 363 - 364 |
Avoid instantiating String objects; this is usually unnecessary. | 366 - 367 |
Violation | Line |
---|---|
Avoid excessively long variable names like currentValidationCommandName | 61 |
Avoid excessively long variable names like currentValidationCommandName | 119 |
Violation | Line |
---|---|
Abstract classes should be named AbstractXXX | 36 - 84 |
A method/constructor shouldn't explicitly throw java.lang.Exception | 55 |
Avoid excessively long variable names like csvFieldValidationContext | 57 |
Avoid excessively long variable names like csvFieldValidationContext | 73 |
A method/constructor shouldn't explicitly throw java.lang.Exception | 74 |
Violation | Line |
---|---|
Avoid excessively long variable names like expectedNumberOfFields | 52 |
Avoid excessively long variable names like expectedNumberOfFields | 125 |
Violation | Line |
---|---|
Avoid excessively long variable names like csvMappingDefinitions | 92 |
Document empty constructor | 118 - 119 |
Overridable method 'init' called during object construction | 137 |
Avoid if (x != y) ..; else ..; | 159 - 160 |
Avoid throwing raw exception types. | 161 |
A method/constructor shouldn't explicitly throw java.lang.Exception | 165 |
Avoid variables with short names like in | 167 |
Substitute calls to size() == 0 (or size() != 0) with calls to isEmpty() | 172 |
A catch statement should never catch throwable since it includes errors. | 177 |
A method/constructor shouldn't explicitly throw java.lang.Exception | 254 |
Avoid variables with short names like o | 255 |
Avoid excessively long variable names like csvMappingDefinition | 277 |
Substitute calls to size() == 0 (or size() != 0) with calls to isEmpty() | 292 |
Avoid if (x != y) ..; else ..; | 295 |
Avoid throwing raw exception types. | 304 |
Avoid if (x != y) ..; else ..; | 311 - 312 |
Substitute calls to size() == 0 (or size() != 0) with calls to isEmpty() | 328 |
Avoid throwing raw exception types. | 333 |
Avoid throwing raw exception types. | 336 |
Avoid excessively long variable names like csvMappingDefinition | 365 |
A method/constructor shouldn't explicitly throw java.lang.Exception | 366 |
Substitute calls to size() == 0 (or size() != 0) with calls to isEmpty() | 367 |
Avoid excessively long variable names like csvFieldMappingList | 368 |
Avoid excessively long variable names like finalPropertyValue | 374 |
Avoid if (x != y) ..; else ..; | 395 - 396 |
Avoid unused method parameters such as 'csvFieldMapping'. | 438 - 460 |
Avoid excessively long variable names like finalPropertyValue | 440 |
A method/constructor shouldn't explicitly throw java.lang.Exception | 441 |
Avoid excessively long variable names like csvMappingDefinitions | 467 |
Use block level rather than method level synchronization | 476 - 478 |
Use block level rather than method level synchronization | 485 - 500 |
Substitute calls to size() == 0 (or size() != 0) with calls to isEmpty() | 491 |
Avoid throwing raw exception types. | 498 |
Violation | Line |
---|---|
Avoid variables with short names like o | 60 |
When instantiating a SimpleDateFormat object, specify a Locale | 83 |
Violation | Line |
---|---|
Avoid excessively long variable names like NO_SPECIAL_CHARACTER_REGEX | 36 |
Avoid excessively long variable names like csvFieldValidationContext | 40 |
A method/constructor shouldn't explicitly throw java.lang.Exception | 41 |
Violation | Line |
---|---|
Avoid instantiating String objects; this is usually unnecessary. | 45 |
Violation | Line |
---|---|
Avoid excessively long variable names like csvFieldValidationContext | 34 |
A method/constructor shouldn't explicitly throw java.lang.Exception | 35 |
Violation | Line |
---|---|
The class 'ObjectToCsvMapper' has a Cyclomatic Complexity of 6 (Highest = 16). | 47 - 246 |
Private field 'mappingDefinition' could be made final; it is only initialized in the declaration or constructor. | 50 |
Avoid throwing raw exception types. | 62 |
A method/constructor shouldn't explicitly throw java.lang.Exception | 66 |
A method/constructor shouldn't explicitly throw java.lang.Exception | 71 |
Avoid excessively long variable names like csvMappingDefinition | 97 |
The method convertObjectToCsv() has an NPath complexity of 18000 | 114 - 209 |
The method 'convertObjectToCsv' has a Cyclomatic Complexity of 16. | 114 - 209 |
A method/constructor shouldn't explicitly throw java.lang.Exception | 115 |
Avoid excessively long variable names like csvMappingDefinition | 118 |
Avoid if (x != y) ..; else ..; | 128 |
Avoid variables with short names like o1 | 132 |
Avoid variables with short names like o2 | 132 |
Avoid excessively long variable names like currentFieldMappingIndex | 154 |
Avoid if (x != y) ..; else ..; | 166 |
Avoid variables with short names like it | 172 |
Avoid if (x != y) ..; else ..; | 187 - 205 |
Avoid excessively long variable names like csvMappingDefinition | 213 |
Avoid if (x != y) ..; else ..; | 217 |
Violation | Line |
---|---|
A method/constructor shouldn't explicitly throw java.lang.Exception | 38 |
Avoid excessively long variable names like csvFieldValidationContext | 46 |
A method/constructor shouldn't explicitly throw java.lang.Exception | 47 |
Violation | Line |
---|---|
Avoid excessively long variable names like POUND_DEFINE_EXPRESSION_START | 46 |
Avoid excessively long variable names like INTERNAL_QUOTATION_MARK | 47 |
Deeply nested if..then statements are hard to read | 69 - 73 |
Avoid if (x != y) ..; else ..; | 76 - 95 |
Avoid variables with short names like o | 99 |
A catch statement should never catch throwable since it includes errors. | 105 |
Avoid throwing raw exception types. | 106 |
Avoid excessively long variable names like currentStringLiteralBuffer | 123 |
Avoid excessively long variable names like massagedStringLiteral | 134 |
Violation | Line |
---|---|
Avoid excessively long variable names like regularExpressions | 39 |
Avoid excessively long variable names like regularExpressions | 45 |
Avoid excessively long variable names like csvFieldValidationContext | 56 |
A method/constructor shouldn't explicitly throw java.lang.Exception | 57 |