The following document contains the results of PMD 4.3.
| Violation | Line |
|---|---|
| A high number of public methods and attributes in an object can indicate the class may need to be broken up for exhaustive testing may prove difficult. | 34 - 1376 |
| Avoid really long Classes. | 60 - 1376 |
| Violation | Line |
|---|---|
| Avoid really long methods. | 356 - 474 |
| Violation | Line |
|---|---|
| A high number of public methods and attributes in an object can indicate the class may need to be broken up for exhaustive testing may prove difficult. | 34 - 647 |
| Violation | Line |
|---|---|
| Avoid really long methods. | 308 - 453 |
| Avoid really long methods. | 461 - 629 |
| Avoid really long methods. | 637 - 783 |
| Violation | Line |
|---|---|
| Avoid unused private fields such as 'MESSAGE_IMAGE_TOO_HEAVY' | 62 |
| Violation | Line |
|---|---|
| Avoid really long methods. | 89 - 210 |
| Avoid really long methods. | 239 - 340 |
| The same String literal appears "');" times in this file. | 299 |
| Violation | Line |
|---|---|
| A high number of public methods and attributes in an object can indicate the class may need to be broken up for exhaustive testing may prove difficult. | 34 - 560 |
| Violation | Line |
|---|---|
| Assigning an Object to null is a code smell. Consider refactoring. | 86 |
| Violation | Line |
|---|---|
| A high number of imports can indicate a high degree of coupling within an object. | 34 - 918 |
| The same String literal appears "<div[^>]+>" times in this file. | 354 |
| The same String literal appears "</div>" times in this file. | 355 |
| Avoid really long methods. | 484 - 627 |
| Avoid really long methods. | 633 - 830 |
| Violation | Line |
|---|---|
| A high number of imports can indicate a high degree of coupling within an object. | 34 - 498 |
| The same String literal appears "digglike.transactionManager" times in this file. | 76 |
| Violation | Line |
|---|---|
| Avoid unused private fields such as 'TAG_FILE_RESOURCE' | 42 |
| Avoid unused private fields such as 'TAG_DOCUMENT_ID' | 43 |
| Avoid unused private fields such as 'TAG_ATTRIBUTE_ID' | 44 |
| Avoid unused private fields such as 'TAG_CONTENT_TYPE' | 45 |
| Violation | Line |
|---|---|
| The same String literal appears "digglike.transactionManager" times in this file. | 54 |
| Violation | Line |
|---|---|
| The same String literal appears "digglike.transactionManager" times in this file. | 59 |
| Violation | Line |
|---|---|
| Avoid calls to overridable methods during construction | 59 |
| Avoid calls to overridable methods during construction | 60 |
| Violation | Line |
|---|---|
| Assigning an Object to null is a code smell. Consider refactoring. | 86 |
| Violation | Line |
|---|---|
| A high number of imports can indicate a high degree of coupling within an object. | 34 - 355 |
| Violation | Line |
|---|---|
| A high number of imports can indicate a high degree of coupling within an object. | 34 - 478 |
| Avoid really long methods. | 90 - 224 |
| Assigning an Object to null is a code smell. Consider refactoring. | 149 |
| Violation | Line |
|---|---|
| A high number of public methods and attributes in an object can indicate the class may need to be broken up for exhaustive testing may prove difficult. | 34 - 1639 |
| A high number of imports can indicate a high degree of coupling within an object. | 34 - 1639 |
| Avoid really long Classes. | 103 - 1639 |
| The same String literal appears "src='image?" times in this file. | 201 |
| Avoid using implementation types like 'ArrayList'; use the interface instead | 1480 |
| Violation | Line |
|---|---|
| Avoid reassigning parameters such as 'texto' | 118 |
| Avoid reassigning parameters such as 'texto' | 118 |
| Avoid reassigning parameters such as 'string' | 137 |
| Avoid reassigning parameters such as 'content' | 233 |
| Avoid reassigning parameters such as 'content' | 233 |
| Avoid reassigning parameters such as 'content' | 233 |
| Avoid reassigning parameters such as 'content' | 233 |
| Avoid reassigning parameters such as 'content' | 252 |
| Avoid really long methods. | 302 - 449 |
| Avoid calls to overridable methods during construction | 479 |
| Violation | Line |
|---|---|
| Assigning an Object to null is a code smell. Consider refactoring. | 351 |
| Assigning an Object to null is a code smell. Consider refactoring. | 354 |
| Violation | Line |
|---|---|
| Avoid really long methods. | 171 - 278 |
| Violation | Line |
|---|---|
| A high number of imports can indicate a high degree of coupling within an object. | 34 - 1993 |
| Avoid really long Classes. | 107 - 1993 |
| Assigning an Object to null is a code smell. Consider refactoring. | 1305 |
| Assigning an Object to null is a code smell. Consider refactoring. | 1349 |
| Assigning an Object to null is a code smell. Consider refactoring. | 1365 |
| Avoid unused formal parameters such as 'method' | 1392 - 1461 |
| Avoid unused formal parameters such as 'method' | 1516 - 1535 |
| Avoid unused formal parameters such as 'method' | 1516 - 1535 |
| Avoid unused formal parameters such as 'method' | 1590 - 1602 |
| Avoid unused formal parameters such as 'method' | 1625 - 1700 |
| Violation | Line |
|---|---|
| A high number of public methods and attributes in an object can indicate the class may need to be broken up for exhaustive testing may prove difficult. | 34 - 3574 |
| A high number of imports can indicate a high degree of coupling within an object. | 34 - 3574 |
| Avoid really long Classes. | 139 - 3574 |
| Avoid unused private fields such as 'FIELD_NOTIFICATION_NEW_COMMENT_SENDER_NAME' | 193 |
| Avoid unused private fields such as 'FIELD_NOTIFICATION_NEW_DIGG_DUBMIT_SENDER_NAME' | 196 |
| Avoid really long methods. | 597 - 752 |
| Avoid really long methods. | 973 - 1083 |
| Avoid really long methods. | 1617 - 1935 |
| Avoid really long methods. | 2044 - 2166 |
| Avoid unused formal parameters such as 'method' | 3047 - 3058 |
| Avoid unused formal parameters such as 'method' | 3069 - 3080 |
| Avoid really long methods. | 3256 - 3420 |
| Assigning an Object to null is a code smell. Consider refactoring. | 3295 |
| Assigning an Object to null is a code smell. Consider refactoring. | 3307 |
| Assigning an Object to null is a code smell. Consider refactoring. | 3364 |
| Assigning an Object to null is a code smell. Consider refactoring. | 3365 |
