SWeDE
| Violation | Line |
|---|---|
| A method should have only one exit point, and that should be the last statement in the method | 44 |
| Violation | Line |
|---|---|
| The class 'OWLCore' has a Cyclomatic Complexity of 3 (Highest = 12). | 49 |
| The method 'addJavaNature' has a Cyclomatic Complexity of 12. | 240 |
| A method should have only one exit point, and that should be the last statement in the method | 387 |
| A method should have only one exit point, and that should be the last statement in the method | 437 |
| A method should have only one exit point, and that should be the last statement in the method | 502 |
| A high number of imports can indicate a high degree of coupling within an object. | 587 |
| A value of 27 may denote a high amount of coupling within the class | 587 |
| Violation | Line |
|---|---|
| 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 | 114 |
| Violation | Line |
|---|---|
| Assigning an Object to null is a code smell. Consider refactoring. | 33 |
| Avoid unused private methods such as 'checkOWLSyntaxBuilder' | 84 |
| Violation | Line |
|---|---|
| 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 | 124 |
| A method should have only one exit point, and that should be the last statement in the method | 130 |
| Avoid unused formal parameters such as 'delta' | 148 |
| A method should have only one exit point, and that should be the last statement in the method | 198 |
| Avoid assigments in operands | 226 |
| Avoid instantiating String objects; this is usually unnecessary. | 275 |
| A method should have only one exit point, and that should be the last statement in the method | 283 |
| A method should have only one exit point, and that should be the last statement in the method | 291 |
| A method should have only one exit point, and that should be the last statement in the method | 303 |
| A method should have only one exit point, and that should be the last statement in the method | 320 |
| A method should have only one exit point, and that should be the last statement in the method | 329 |
| Violation | Line |
|---|---|
| Avoid unnecessary constructors - the compiler will generate these for you | 33 |
| Violation | Line |
|---|---|
| The class 'SWProjectInfo' has a Cyclomatic Complexity of 3 (Highest = 11). | 64 |
| A method should have only one exit point, and that should be the last statement in the method | 135 |
| Avoid instantiating String objects; this is usually unnecessary. | 143 |
| A method should have only one exit point, and that should be the last statement in the method | 149 |
| The same String literal appears 4 times in this file; the first occurrence is on line 161 | 161 |
| A method should have only one exit point, and that should be the last statement in the method | 162 |
| A method should have only one exit point, and that should be the last statement in the method | 167 |
| 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 | 255 |
| A method should have only one exit point, and that should be the last statement in the method | 260 |
| A method should have only one exit point, and that should be the last statement in the method | 268 |
| Avoid really long methods. | 283 |
| The method 'refreshInfoFile' has a Cyclomatic Complexity of 11. | 283 |
| A method should have only one exit point, and that should be the last statement in the method | 297 |
| A method should have only one exit point, and that should be the last statement in the method | 302 |
| A method should have only one exit point, and that should be the last statement in the method | 433 |
| A method should have only one exit point, and that should be the last statement in the method | 449 |
| A method should have only one exit point, and that should be the last statement in the method | 482 |
| A method should have only one exit point, and that should be the last statement in the method | 488 |
| Avoid unused local variables such as 'librariesTag' | 509 |
| A method should have only one exit point, and that should be the last statement in the method | 584 |
| A method should have only one exit point, and that should be the last statement in the method | 614 |
| A method should have only one exit point, and that should be the last statement in the method | 626 |
| A method should have only one exit point, and that should be the last statement in the method | 631 |
| A method should have only one exit point, and that should be the last statement in the method | 653 |
| A method should have only one exit point, and that should be the last statement in the method | 657 |
| A method should have only one exit point, and that should be the last statement in the method | 662 |
| A method should have only one exit point, and that should be the last statement in the method | 678 |
| A method should have only one exit point, and that should be the last statement in the method | 685 |
| Avoid unused private methods such as 'getUniqueTag' | 711 |
| A method should have only one exit point, and that should be the last statement in the method | 726 |
| A method should have only one exit point, and that should be the last statement in the method | 743 |
| A high number of imports can indicate a high degree of coupling within an object. | 766 |
| A value of 34 may denote a high amount of coupling within the class | 766 |
| Violation | Line |
|---|---|
| The class 'AttributeNode' has a Cyclomatic Complexity of 3 (Highest = 10). | 22 |
| Avoid calls to overridable methods during construction | 31 |
| A method should have only one exit point, and that should be the last statement in the method | 160 |
| A method should have only one exit point, and that should be the last statement in the method | 212 |
| 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 | 216 |
| 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 | 220 |
| A method should have only one exit point, and that should be the last statement in the method | 222 |
| The method 'create' has a Cyclomatic Complexity of 10. | 239 |
| A method should have only one exit point, and that should be the last statement in the method | 244 |
| A method should have only one exit point, and that should be the last statement in the method | 269 |
| A method should have only one exit point, and that should be the last statement in the method | 273 |
| A method should have only one exit point, and that should be the last statement in the method | 285 |
| A method should have only one exit point, and that should be the last statement in the method | 291 |
| Violation | Line |
|---|---|
| The class 'ClassNode' has a Cyclomatic Complexity of 3 (Highest = 11). | 29 |
| The method 'createJenaResource' has a Cyclomatic Complexity of 11. | 120 |
| Avoid empty catch blocks | 153 |
| A method should have only one exit point, and that should be the last statement in the method | 173 |
| Avoid unused local variables such as 'res' | 206 |
| Avoid unused local variables such as 'tag' | 229 |
| Violation | Line |
|---|---|
| A method should have only one exit point, and that should be the last statement in the method | 128 |
| Violation | Line |
|---|---|
| A method should have only one exit point, and that should be the last statement in the method | 72 |
| A method should have only one exit point, and that should be the last statement in the method | 78 |
| 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 | 124 |
| A method should have only one exit point, and that should be the last statement in the method | 161 |
| A method should have only one exit point, and that should be the last statement in the method | 166 |
| A method should have only one exit point, and that should be the last statement in the method | 172 |
| Violation | Line |
|---|---|
| A method should have only one exit point, and that should be the last statement in the method | 89 |
| A method should have only one exit point, and that should be the last statement in the method | 95 |
| 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 | 141 |
| Violation | Line |
|---|---|
| A method should have only one exit point, and that should be the last statement in the method | 94 |
| 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 | 114 |
| A method should have only one exit point, and that should be the last statement in the method | 146 |
| Violation | Line |
|---|---|
| A method should have only one exit point, and that should be the last statement in the method | 65 |
| Violation | Line |
|---|---|
| Avoid really long Classes. | 62 |
| The class 'OAST' has a Cyclomatic Complexity of 3 (Highest = 12). | 62 |
| The same String literal appears 6 times in this file; the first occurrence is on line 102 | 102 |
| The same String literal appears 6 times in this file; the first occurrence is on line 120 | 120 |
| 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 | 236 |
| Avoid empty catch blocks | 273 |
| A method should have only one exit point, and that should be the last statement in the method | 284 |
| A method should have only one exit point, and that should be the last statement in the method | 290 |
| A method should have only one exit point, and that should be the last statement in the method | 294 |
| Ensure you override both equals() and hashCode() | 299 |
| A method should have only one exit point, and that should be the last statement in the method | 344 |
| The method 'restorePersistedUnparseables' has a Cyclomatic Complexity of 12. | 363 |
| Ensure you override both equals() and hashCode() | 401 |
| Avoid instantiating String objects; this is usually unnecessary. | 423 |
| Avoid reassigning parameters such as 'node' | 556 |
| A method should have only one exit point, and that should be the last statement in the method | 659 |
| A method should have only one exit point, and that should be the last statement in the method | 680 |
| The same String literal appears 4 times in this file; the first occurrence is on line 733 | 733 |
| A method should have only one exit point, and that should be the last statement in the method | 773 |
| A method should have only one exit point, and that should be the last statement in the method | 789 |
| A method should have only one exit point, and that should be the last statement in the method | 807 |
| A method should have only one exit point, and that should be the last statement in the method | 812 |
| Avoid really long methods. | 846 |
| The method 'replace' has a Cyclomatic Complexity of 10. | 846 |
| Avoid calling toString() on String objects; this is unnecessary | 930 |
| Avoid calling toString() on String objects; this is unnecessary | 986 |
| Avoid unused local variables such as 'delta' | 1180 |
| Avoid empty catch blocks | 1274 |
| Avoid really long methods. | 1604 |
| Avoid reassigning parameters such as 'parent' | 1604 |
| Avoid reassigning parameters such as 'sProlog' | 1604 |
| The method 'partialParse' has a Cyclomatic Complexity of 10. | 1604 |
| A method should have only one exit point, and that should be the last statement in the method | 1654 |
| A method should have only one exit point, and that should be the last statement in the method | 1706 |
| A method should have only one exit point, and that should be the last statement in the method | 1733 |
| Avoid empty catch blocks | 1737 |
| Avoid empty catch blocks | 1740 |
| Avoid empty catch blocks | 1743 |
| Avoid empty catch blocks | 1746 |
| A method should have only one exit point, and that should be the last statement in the method | 1755 |
| A method should have only one exit point, and that should be the last statement in the method | 1763 |
| Avoid reassigning parameters such as 'uri' | 1830 |
| A method should have only one exit point, and that should be the last statement in the method | 1835 |
| A method should have only one exit point, and that should be the last statement in the method | 1857 |
| A method should have only one exit point, and that should be the last statement in the method | 2066 |
| Assigning an Object to null is a code smell. Consider refactoring. | 2096 |
| Assigning an Object to null is a code smell. Consider refactoring. | 2120 |
| A high number of imports can indicate a high degree of coupling within an object. | 2133 |
| A value of 47 may denote a high amount of coupling within the class | 2133 |
| Violation | Line |
|---|---|
| The class 'OASTDelta' has a Cyclomatic Complexity of 4 (Highest = 25). | 24 |
| Assigning an Object to null is a code smell. Consider refactoring. | 124 |
| Assigning an Object to null is a code smell. Consider refactoring. | 137 |
| 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 | 209 |
| A method should have only one exit point, and that should be the last statement in the method | 231 |
| A method should have only one exit point, and that should be the last statement in the method | 254 |
| Avoid assigments in operands | 282 |
| A method should have only one exit point, and that should be the last statement in the method | 304 |
| A method should have only one exit point, and that should be the last statement in the method | 312 |
| Avoid really long methods. | 326 |
| The method 'createChildDeltas' has a Cyclomatic Complexity of 25. | 326 |
| A method should have only one exit point, and that should be the last statement in the method | 356 |
| A method should have only one exit point, and that should be the last statement in the method | 374 |
| A method should have only one exit point, and that should be the last statement in the method | 403 |
| A method should have only one exit point, and that should be the last statement in the method | 421 |
| A method should have only one exit point, and that should be the last statement in the method | 584 |
| A method should have only one exit point, and that should be the last statement in the method | 589 |
| The method 'findMatch' has a Cyclomatic Complexity of 11. | 615 |
| A method should have only one exit point, and that should be the last statement in the method | 625 |
| A method should have only one exit point, and that should be the last statement in the method | 637 |
| A method should have only one exit point, and that should be the last statement in the method | 642 |
| A method should have only one exit point, and that should be the last statement in the method | 653 |
| A method should have only one exit point, and that should be the last statement in the method | 658 |
| A method should have only one exit point, and that should be the last statement in the method | 726 |
| A method should have only one exit point, and that should be the last statement in the method | 733 |
| Assigning an Object to null is a code smell. Consider refactoring. | 743 |
| Violation | Line |
|---|---|
| The class 'OASTEvent' has a Cyclomatic Complexity of 3 (Highest = 10). | 20 |
| The constructor 'OASTEvent' has a Cyclomatic Complexity of 10. | 142 |
| 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 | 267 |
| Assigning an Object to null is a code smell. Consider refactoring. | 438 |
| Deeply nested if..then statements are hard to read | 440 |
| 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 | 527 |
| 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 | 538 |
| A method should have only one exit point, and that should be the last statement in the method | 557 |
| A method should have only one exit point, and that should be the last statement in the method | 561 |
| Assigning an Object to null is a code smell. Consider refactoring. | 591 |
| Assigning an Object to null is a code smell. Consider refactoring. | 600 |
| Violation | Line |
|---|---|
| A method should have only one exit point, and that should be the last statement in the method | 180 |
| Violation | Line |
|---|---|
| Avoid really long Classes. | 30 |
| A method should have only one exit point, and that should be the last statement in the method | 664 |
| A method should have only one exit point, and that should be the last statement in the method | 668 |
| A method should have only one exit point, and that should be the last statement in the method | 672 |
| A method should have only one exit point, and that should be the last statement in the method | 690 |
| A method should have only one exit point, and that should be the last statement in the method | 694 |
| A method should have only one exit point, and that should be the last statement in the method | 698 |
| A method should have only one exit point, and that should be the last statement in the method | 716 |
| A method should have only one exit point, and that should be the last statement in the method | 720 |
| A method should have only one exit point, and that should be the last statement in the method | 724 |
| A method should have only one exit point, and that should be the last statement in the method | 741 |
| A method should have only one exit point, and that should be the last statement in the method | 745 |
| A method should have only one exit point, and that should be the last statement in the method | 749 |
| A method should have only one exit point, and that should be the last statement in the method | 766 |
| A method should have only one exit point, and that should be the last statement in the method | 770 |
| A method should have only one exit point, and that should be the last statement in the method | 774 |
| A method should have only one exit point, and that should be the last statement in the method | 790 |
| A method should have only one exit point, and that should be the last statement in the method | 795 |
| A method should have only one exit point, and that should be the last statement in the method | 804 |
| A method should have only one exit point, and that should be the last statement in the method | 806 |
| A method should have only one exit point, and that should be the last statement in the method | 813 |
| A method should have only one exit point, and that should be the last statement in the method | 815 |
| A method should have only one exit point, and that should be the last statement in the method | 822 |
| A method should have only one exit point, and that should be the last statement in the method | 824 |
| A method should have only one exit point, and that should be the last statement in the method | 936 |
| A method should have only one exit point, and that should be the last statement in the method | 997 |
| A method should have only one exit point, and that should be the last statement in the method | 1125 |
| A method should have only one exit point, and that should be the last statement in the method | 1145 |
| A method should have only one exit point, and that should be the last statement in the method | 1214 |
| A method should have only one exit point, and that should be the last statement in the method | 1237 |
| A method should have only one exit point, and that should be the last statement in the method | 1243 |
| A method should have only one exit point, and that should be the last statement in the method | 1258 |
| A method should have only one exit point, and that should be the last statement in the method | 1277 |
| A method should have only one exit point, and that should be the last statement in the method | 1279 |
| A method should have only one exit point, and that should be the last statement in the method | 1306 |
| Avoid reassigning parameters such as 'other' | 1320 |
| A method should have only one exit point, and that should be the last statement in the method | 1426 |
| A method should have only one exit point, and that should be the last statement in the method | 1430 |
| A method should have only one exit point, and that should be the last statement in the method | 1444 |
| A method should have only one exit point, and that should be the last statement in the method | 1451 |
| A method should have only one exit point, and that should be the last statement in the method | 1479 |
| A method should have only one exit point, and that should be the last statement in the method | 1532 |
| A method should have only one exit point, and that should be the last statement in the method | 1537 |
| Assigning an Object to null is a code smell. Consider refactoring. | 1772 |
| A method should have only one exit point, and that should be the last statement in the method | 1822 |
| Assigning an Object to null is a code smell. Consider refactoring. | 1862 |
| Violation | Line |
|---|---|
| The same String literal appears 4 times in this file; the first occurrence is on line 88 | 88 |
| 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 | 191 |
| Violation | Line |
|---|---|
| The class 'PropertyNode' has a Cyclomatic Complexity of 4 (Highest = 12). | 35 |
| A method should have only one exit point, and that should be the last statement in the method | 126 |
| A method should have only one exit point, and that should be the last statement in the method | 131 |
| A method should have only one exit point, and that should be the last statement in the method | 137 |
| A method should have only one exit point, and that should be the last statement in the method | 144 |
| Avoid empty catch blocks | 164 |
| The method 'createObject' has a Cyclomatic Complexity of 12. | 183 |
| A method should have only one exit point, and that should be the last statement in the method | 202 |
| 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 | 469 |
| A method should have only one exit point, and that should be the last statement in the method | 478 |
| A method should have only one exit point, and that should be the last statement in the method | 482 |
| Violation | Line |
|---|---|
| The class 'TagNode' has a Cyclomatic Complexity of 5 (Highest = 56). | 70 |
| Avoid calls to overridable methods during construction | 77 |
| Avoid calls to overridable methods during construction | 90 |
| Assigning an Object to null is a code smell. Consider refactoring. | 202 |
| Assigning an Object to null is a code smell. Consider refactoring. | 203 |
| A method should have only one exit point, and that should be the last statement in the method | 205 |
| Assigning an Object to null is a code smell. Consider refactoring. | 210 |
| 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 | 360 |
| A method should have only one exit point, and that should be the last statement in the method | 433 |
| A method should have only one exit point, and that should be the last statement in the method | 447 |
| A method should have only one exit point, and that should be the last statement in the method | 634 |
| A method should have only one exit point, and that should be the last statement in the method | 638 |
| A method should have only one exit point, and that should be the last statement in the method | 642 |
| Avoid really long methods. | 692 |
| The method 'create' has a Cyclomatic Complexity of 56. | 692 |
| A method should have only one exit point, and that should be the last statement in the method | 697 |
| A method should have only one exit point, and that should be the last statement in the method | 699 |
| A method should have only one exit point, and that should be the last statement in the method | 701 |
| A method should have only one exit point, and that should be the last statement in the method | 703 |
| A method should have only one exit point, and that should be the last statement in the method | 705 |
| A method should have only one exit point, and that should be the last statement in the method | 707 |
| A method should have only one exit point, and that should be the last statement in the method | 709 |
| A method should have only one exit point, and that should be the last statement in the method | 711 |
| A method should have only one exit point, and that should be the last statement in the method | 713 |
| A method should have only one exit point, and that should be the last statement in the method | 715 |
| A method should have only one exit point, and that should be the last statement in the method | 717 |
| A method should have only one exit point, and that should be the last statement in the method | 719 |
| A method should have only one exit point, and that should be the last statement in the method | 721 |
| A method should have only one exit point, and that should be the last statement in the method | 723 |
| A method should have only one exit point, and that should be the last statement in the method | 725 |
| A method should have only one exit point, and that should be the last statement in the method | 727 |
| A method should have only one exit point, and that should be the last statement in the method | 729 |
| A method should have only one exit point, and that should be the last statement in the method | 731 |
| A method should have only one exit point, and that should be the last statement in the method | 733 |
| A method should have only one exit point, and that should be the last statement in the method | 735 |
| A method should have only one exit point, and that should be the last statement in the method | 737 |
| A method should have only one exit point, and that should be the last statement in the method | 739 |
| A method should have only one exit point, and that should be the last statement in the method | 741 |
| A method should have only one exit point, and that should be the last statement in the method | 743 |
| A method should have only one exit point, and that should be the last statement in the method | 745 |
| A method should have only one exit point, and that should be the last statement in the method | 747 |
| A method should have only one exit point, and that should be the last statement in the method | 749 |
| A method should have only one exit point, and that should be the last statement in the method | 751 |
| A method should have only one exit point, and that should be the last statement in the method | 753 |
| A method should have only one exit point, and that should be the last statement in the method | 755 |
| A method should have only one exit point, and that should be the last statement in the method | 757 |
| A method should have only one exit point, and that should be the last statement in the method | 759 |
| A method should have only one exit point, and that should be the last statement in the method | 761 |
| A method should have only one exit point, and that should be the last statement in the method | 763 |
| A method should have only one exit point, and that should be the last statement in the method | 765 |
| A method should have only one exit point, and that should be the last statement in the method | 767 |
| A method should have only one exit point, and that should be the last statement in the method | 769 |
| A method should have only one exit point, and that should be the last statement in the method | 771 |
| A method should have only one exit point, and that should be the last statement in the method | 773 |
| A method should have only one exit point, and that should be the last statement in the method | 775 |
| A method should have only one exit point, and that should be the last statement in the method | 777 |
| A method should have only one exit point, and that should be the last statement in the method | 779 |
| A method should have only one exit point, and that should be the last statement in the method | 781 |
| A method should have only one exit point, and that should be the last statement in the method | 783 |
| A method should have only one exit point, and that should be the last statement in the method | 785 |
| A method should have only one exit point, and that should be the last statement in the method | 787 |
| A method should have only one exit point, and that should be the last statement in the method | 789 |
| A method should have only one exit point, and that should be the last statement in the method | 791 |
| A method should have only one exit point, and that should be the last statement in the method | 793 |
| A method should have only one exit point, and that should be the last statement in the method | 795 |
| A method should have only one exit point, and that should be the last statement in the method | 797 |
| A method should have only one exit point, and that should be the last statement in the method | 799 |
| A method should have only one exit point, and that should be the last statement in the method | 801 |
| A method should have only one exit point, and that should be the last statement in the method | 803 |
| The method 'create' has a Cyclomatic Complexity of 16. | 827 |
| A method should have only one exit point, and that should be the last statement in the method | 834 |
| A method should have only one exit point, and that should be the last statement in the method | 838 |
| A method should have only one exit point, and that should be the last statement in the method | 842 |
| A method should have only one exit point, and that should be the last statement in the method | 887 |
| A method should have only one exit point, and that should be the last statement in the method | 899 |
| A method should have only one exit point, and that should be the last statement in the method | 904 |
| A method should have only one exit point, and that should be the last statement in the method | 908 |
| A high number of imports can indicate a high degree of coupling within an object. | 932 |
| Violation | Line |
|---|---|
| A method should have only one exit point, and that should be the last statement in the method | 65 |
| 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 | 69 |
| A method should have only one exit point, and that should be the last statement in the method | 71 |
| 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 | 75 |
| Violation | Line |
|---|---|
| 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 | 67 |
| A method should have only one exit point, and that should be the last statement in the method | 90 |
| Avoid reassigning parameters such as 'b' | 113 |
| Avoid reassigning parameters such as 'b' | 135 |
| Violation | Line |
|---|---|
| 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 | 67 |
| A method should have only one exit point, and that should be the last statement in the method | 91 |
| Avoid reassigning parameters such as 'b' | 114 |
| Avoid reassigning parameters such as 'b' | 135 |
| Violation | Line |
|---|---|
| Avoid unnecessary constructors - the compiler will generate these for you | 28 |
| Avoid unused private fields such as 'S_DOCTYPE' | 33 |
| Violation | Line |
|---|---|
| Avoid unused private fields such as '_list' | 24 |
| A method should have only one exit point, and that should be the last statement in the method | 54 |
| Violation | Line |
|---|---|
| Avoid unused local variables such as 'newKey' | 39 |
| Avoid unused local variables such as 'suffix' | 40 |
| Violation | Line |
|---|---|
| Avoid instantiation through private constructors from outside of the constructor's class. | 58 |
| Avoid instantiation through private constructors from outside of the constructor's class. | 62 |
| Deeply nested if..then statements are hard to read | 168 |
| Violation | Line |
|---|---|
| Avoid unused private fields such as '_progressMonitor' | 36 |
| Avoid unused local variables such as 'chunksDownloaded' | 148 |
| Avoid unused local variables such as 'error' | 150 |
| Violation | Line |
|---|---|
| Avoid unused local variables such as 'rjl' | 93 |
| Avoid unused local variables such as 'lc' | 237 |
| Avoid unused local variables such as 'libraryIterator' | 285 |
| Violation | Line |
|---|---|
| The same String literal appears 5 times in this file; the first occurrence is on line 107 | 107 |
| Assigning an Object to null is a code smell. Consider refactoring. | 130 |
| Avoid unused local variables such as 'newLed' | 279 |
| Avoid unused local variables such as 'newFile' | 280 |
| Avoid unused local variables such as 'libraryEntryDescriptor' | 405 |
| The same String literal appears 4 times in this file; the first occurrence is on line 440 | 440 |
| The same String literal appears 4 times in this file; the first occurrence is on line 442 | 442 |
| Avoid unused local variables such as 'newEntry' | 547 |
| A value of 31 may denote a high amount of coupling within the class | 667 |
| Violation | Line |
|---|---|
| Avoid calls to overridable methods during construction | 104 |
| Avoid unused local variables such as 'lse' | 271 |
| Avoid unused local variables such as 'led' | 358 |
| Avoid unused local variables such as 'lec' | 359 |
| Avoid unused local variables such as 'downloadURL' | 360 |
| Avoid unused local variables such as 'i' | 361 |
| Avoid unused local variables such as 'numEntries' | 362 |
| Ensure you override both equals() and hashCode() | 515 |
| A value of 34 may denote a high amount of coupling within the class | 756 |
| Violation | Line |
|---|---|
| Avoid using implementation types like 'HashMap'; use the interface instead | 61 |
| Avoid instantiation through private constructors from outside of the constructor's class. | 105 |
| A method should have only one exit point, and that should be the last statement in the method | 914 |
| A high number of imports can indicate a high degree of coupling within an object. | 952 |
| 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. | 952 |
| A value of 28 may denote a high amount of coupling within the class | 952 |
| Violation | Line |
|---|---|
| The class 'LibraryStructuralEdit' has a Cyclomatic Complexity of 3 (Highest = 13). | 73 |
| Assigning an Object to null is a code smell. Consider refactoring. | 93 |
| Assigning an Object to null is a code smell. Consider refactoring. | 94 |
| Assigning an Object to null is a code smell. Consider refactoring. | 95 |
| Assigning an Object to null is a code smell. Consider refactoring. | 96 |
| Avoid really long methods. | 240 |
| The method 'perform' has a Cyclomatic Complexity of 13. | 240 |
| The same String literal appears 5 times in this file; the first occurrence is on line 249 | 249 |
| A high ratio of statements to labels in a switch statement. Consider refactoring. | 252 |
| Assigning an Object to null is a code smell. Consider refactoring. | 264 |
| The same String literal appears 5 times in this file; the first occurrence is on line 275 | 275 |
| Avoid unused local variables such as 'totalBytesDownloaded' | 389 |
| Violation | Line |
|---|---|
| Assigning an Object to null is a code smell. Consider refactoring. | 76 |
| Assigning an Object to null is a code smell. Consider refactoring. | 83 |
| Violation | Line |
|---|---|
| A method should have only one exit point, and that should be the last statement in the method | 58 |
| Violation | Line |
|---|---|
| A method should have only one exit point, and that should be the last statement in the method | 81 |
| A method should have only one exit point, and that should be the last statement in the method | 94 |
| A method should have only one exit point, and that should be the last statement in the method | 107 |
| 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 | 128 |
| A method should have only one exit point, and that should be the last statement in the method | 134 |
| A method should have only one exit point, and that should be the last statement in the method | 151 |
| Violation | Line |
|---|---|
| A method should have only one exit point, and that should be the last statement in the method | 72 |
| A method should have only one exit point, and that should be the last statement in the method | 76 |
| 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 | 207 |
| Violation | Line |
|---|---|
| Avoid calls to overridable methods during construction | 67 |
| Violation | Line |
|---|---|
| A method should have only one exit point, and that should be the last statement in the method | 44 |
| A method should have only one exit point, and that should be the last statement in the method | 50 |
| A method should have only one exit point, and that should be the last statement in the method | 65 |
| A method should have only one exit point, and that should be the last statement in the method | 74 |
| A method should have only one exit point, and that should be the last statement in the method | 88 |
| 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 | 113 |
| A method should have only one exit point, and that should be the last statement in the method | 117 |
| Violation | Line |
|---|---|
| The class 'OWLModel' has a Cyclomatic Complexity of 3 (Highest = 10). | 49 |
| Assigning an Object to null is a code smell. Consider refactoring. | 61 |
| 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 | 148 |
| A method should have only one exit point, and that should be the last statement in the method | 175 |
| Avoid unused private methods such as 'checkBuilders' | 318 |
| A method should have only one exit point, and that should be the last statement in the method | 387 |
| Avoid unused formal parameters such as 'c' | 398 |
| Avoid unused formal parameters such as 'p' | 407 |
| The method 'add' has a Cyclomatic Complexity of 10. | 416 |
| A method should have only one exit point, and that should be the last statement in the method | 420 |
| 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 | 428 |
| A method should have only one exit point, and that should be the last statement in the method | 432 |
| A method should have only one exit point, and that should be the last statement in the method | 438 |
| A method should have only one exit point, and that should be the last statement in the method | 446 |
| A method should have only one exit point, and that should be the last statement in the method | 451 |
| A method should have only one exit point, and that should be the last statement in the method | 458 |
| A method should have only one exit point, and that should be the last statement in the method | 462 |
| Avoid unused private methods such as 'trace' | 478 |
| Violation | Line |
|---|---|
| The class 'OWLModelDeltaVisitor' has a Cyclomatic Complexity of 4 (Highest = 10). | 29 |
| Avoid unused private methods such as 'printDetailFlag' | 62 |
| The method 'printDetailFlag' has a Cyclomatic Complexity of 10. | 62 |
| A method should have only one exit point, and that should be the last statement in the method | 107 |
| A method should have only one exit point, and that should be the last statement in the method | 123 |
| A method should have only one exit point, and that should be the last statement in the method | 129 |
| Avoid unused formal parameters such as 'delta' | 167 |
| A method should have only one exit point, and that should be the last statement in the method | 172 |
| A method should have only one exit point, and that should be the last statement in the method | 191 |
| 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 | 61 |
| 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 | 82 |
| A method should have only one exit point, and that should be the last statement in the method | 91 |
| 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 | 149 |
| A method should have only one exit point, and that should be the last statement in the method | 162 |
| A method should have only one exit point, and that should be the last statement in the method | 166 |
| A method should have only one exit point, and that should be the last statement in the method | 196 |
| A method should have only one exit point, and that should be the last statement in the method | 205 |
| Violation | Line |
|---|---|
| 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 | 161 |
| Avoid unused local variables such as 'uri' | 165 |
| A method should have only one exit point, and that should be the last statement in the method | 253 |
| A method should have only one exit point, and that should be the last statement in the method | 263 |
| A method should have only one exit point, and that should be the last statement in the method | 269 |
| A method should have only one exit point, and that should be the last statement in the method | 298 |
| A method should have only one exit point, and that should be the last statement in the method | 311 |
| A method should have only one exit point, and that should be the last statement in the method | 344 |
| A method should have only one exit point, and that should be the last statement in the method | 348 |
| A method should have only one exit point, and that should be the last statement in the method | 352 |
| A method should have only one exit point, and that should be the last statement in the method | 356 |
| A method should have only one exit point, and that should be the last statement in the method | 374 |
| A method should have only one exit point, and that should be the last statement in the method | 424 |
| Avoid unused formal parameters such as 'message' | 501 |
| Avoid unused formal parameters such as 'user' | 501 |
| Avoid unused formal parameters such as 'error' | 505 |
| Avoid unused formal parameters such as 'msg' | 505 |
| A high number of imports can indicate a high degree of coupling within an object. | 511 |
| A value of 33 may denote a high amount of coupling within the class | 511 |
| Violation | Line |
|---|---|
| Assigning an Object to null is a code smell. Consider refactoring. | 135 |
| A method should have only one exit point, and that should be the last statement in the method | 159 |
| A method should have only one exit point, and that should be the last statement in the method | 314 |
| A method should have only one exit point, and that should be the last statement in the method | 318 |
| Violation | Line |
|---|---|
| A method should have only one exit point, and that should be the last statement in the method | 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 | 108 |
| A method should have only one exit point, and that should be the last statement in the method | 112 |
| A method should have only one exit point, and that should be the last statement in the method | 116 |
| 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 | 124 |
| Violation | Line |
|---|---|
| The class 'OWLDelayedSyntaxChecker' has a Cyclomatic Complexity of 3 (Highest = 12). | 28 |
| Assigning an Object to null is a code smell. Consider refactoring. | 144 |
| Avoid really long methods. | 193 |
| The method 'addDocumentEvent' has a Cyclomatic Complexity of 12. | 193 |
| Avoid instantiating String objects; this is usually unnecessary. | 234 |
| Assigning an Object to null is a code smell. Consider refactoring. | 308 |
| Violation | Line |
|---|---|
| The class 'OASTUpdater' has a Cyclomatic Complexity of 3 (Highest = 20). | 54 |
| Avoid really long methods. | 247 |
| The method 'handleEvent' has a Cyclomatic Complexity of 20. | 247 |
| Deeply nested if..then statements are hard to read | 310 |
| If you override finalize(), make it protected | 561 |
| Violation | Line |
|---|---|
| The same String literal appears 4 times in this file; the first occurrence is on line 154 | 154 |
| Avoid reassigning parameters such as 'input' | 245 |
| A method should have only one exit point, and that should be the last statement in the method | 329 |
| A method should have only one exit point, and that should be the last statement in the method | 333 |
| A method should have only one exit point, and that should be the last statement in the method | 375 |
| A method should have only one exit point, and that should be the last statement in the method | 381 |
| A value of 24 may denote a high amount of coupling within the class | 387 |
| Violation | Line |
|---|---|
| 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 | 102 |
| Violation | Line |
|---|---|
| The same String literal appears 4 times in this file; the first occurrence is on line 73 | 73 |
| Violation | Line |
|---|---|
| The class 'OWLSourceEditor' has a Cyclomatic Complexity of 2 (Highest = 10). | 40 |
| The method 'insertNode' has a Cyclomatic Complexity of 10. | 233 |
| Violation | Line |
|---|---|
| Avoid unused private fields such as '_indentStrategy' | 62 |
| A method should have only one exit point, and that should be the last statement in the method | 207 |
| A method should have only one exit point, and that should be the last statement in the method | 239 |
| A method should have only one exit point, and that should be the last statement in the method | 260 |
| A method should have only one exit point, and that should be the last statement in the method | 377 |
| A high number of imports can indicate a high degree of coupling within an object. | 455 |
| A value of 31 may denote a high amount of coupling within the class | 455 |
| Violation | Line |
|---|---|
| The class 'DefaultNamespaceSuggester' has a Cyclomatic Complexity of 3 (Highest = 10). | 41 |
| Avoid unused local variables such as 'allStrings' | 57 |
| Avoid calls to overridable methods during construction | 128 |
| The same String literal appears 4 times in this file; the first occurrence is on line 215 | 215 |
| The method 'getPropertiesFromTree' has a Cyclomatic Complexity of 10. | 242 |
| The same String literal appears 6 times in this file; the first occurrence is on line 257 | 257 |
| Avoid unused local variables such as 'name' | 310 |
| Avoid reassigning parameters such as 'alreadyTyped' | 403 |
| Avoid unused local variables such as 'allStrings' | 405 |
| Violation | Line |
|---|---|
| Avoid really long Classes. | 62 |
| The class 'DefaultOWLContentAssistProcessor' has a Cyclomatic Complexity of 5 (Highest = 11). | 62 |
| The method 'resourceChanged' has a Cyclomatic Complexity of 11. | 148 |
| Deeply nested if..then statements are hard to read | 168 |
| The same String literal appears 11 times in this file; the first occurrence is on line 175 | 175 |
| Avoid unused local variables such as 'tempURI' | 233 |
| Avoid unused local variables such as 'tempNamespace' | 234 |
| Avoid unused local variables such as 'i' | 237 |
| Avoid unused local variables such as 'found' | 238 |
| Avoid unused local variables such as 'namespace' | 340 |
| Avoid using implementation types like 'HashSet'; use the interface instead | 361 |
| Avoid using implementation types like 'HashSet'; use the interface instead | 366 |
| Avoid empty catch blocks | 419 |
| A method should have only one exit point, and that should be the last statement in the method | 608 |
| A method should have only one exit point, and that should be the last statement in the method | 623 |
| A method should have only one exit point, and that should be the last statement in the method | 627 |
| A method should have only one exit point, and that should be the last statement in the method | 632 |
| The same String literal appears 8 times in this file; the first occurrence is on line 660 | 660 |
| Avoid reassigning parameters such as 'alreadyTyped' | 679 |
| The method 'extractNamespaceOrURI' has a Cyclomatic Complexity of 11. | 679 |
| The same String literal appears 10 times in this file; the first occurrence is on line 684 | 684 |
| Avoid reassigning parameters such as 'sURI' | 822 |
| Avoid empty catch blocks | 872 |
| The method 'handleLessThan' has a Cyclomatic Complexity of 10. | 944 |
| The method 'computeCompletionProposals' has a Cyclomatic Complexity of 10. | 1027 |
| Avoid unused local variables such as 'i' | 1043 |
| Avoid unused local variables such as 'tempNamespace' | 1044 |
| Avoid unused local variables such as 'tempNamespaceSuggestions' | 1045 |
| Avoid unused local variables such as 'proposalStrings' | 1047 |
| Avoid unused local variables such as 'type' | 1049 |
| Avoid empty catch blocks | 1076 |
| Avoid unused local variables such as 'library' | 1117 |
| Avoid unused local variables such as 'icon' | 1231 |
| A high number of imports can indicate a high degree of coupling within an object. | 1424 |
| A value of 34 may denote a high amount of coupling within the class | 1424 |
| Violation | Line |
|---|---|
| Ensure you override both equals() and hashCode() | 45 |
| Deeply nested if..then statements are hard to read | 54 |
| Violation | Line |
|---|---|
| A method should have only one exit point, and that should be the last statement in the method | 149 |
| A method should have only one exit point, and that should be the last statement in the method | 177 |
| Avoid unused formal parameters such as 'offsetAtt' | 232 |
| A method should have only one exit point, and that should be the last statement in the method | 287 |
| A method should have only one exit point, and that should be the last statement in the method | 303 |
| Violation | Line |
|---|---|
| A method should have only one exit point, and that should be the last statement in the method | 201 |
| A method should have only one exit point, and that should be the last statement in the method | 264 |
| A method should have only one exit point, and that should be the last statement in the method | 271 |
| A method should have only one exit point, and that should be the last statement in the method | 289 |
| A method should have only one exit point, and that should be the last statement in the method | 298 |
| A method should have only one exit point, and that should be the last statement in the method | 326 |
| A method should have only one exit point, and that should be the last statement in the method | 363 |
| A method should have only one exit point, and that should be the last statement in the method | 398 |
| A method should have only one exit point, and that should be the last statement in the method | 402 |
| A method should have only one exit point, and that should be the last statement in the method | 439 |
| Violation | Line |
|---|---|
| Avoid unused local variables such as 'prevLine' | 105 |
| A method should have only one exit point, and that should be the last statement in the method | 205 |
| A method should have only one exit point, and that should be the last statement in the method | 236 |
| A method should have only one exit point, and that should be the last statement in the method | 261 |
| Avoid unused local variables such as 'oldIndent' | 343 |
| A method should have only one exit point, and that should be the last statement in the method | 373 |
| A method should have only one exit point, and that should be the last statement in the method | 385 |
| Avoid unused private methods such as 'isMatchingTag' | 458 |
| A method should have only one exit point, and that should be the last statement in the method | 464 |
| A method should have only one exit point, and that should be the last statement in the method | 483 |
| Avoid really long methods. | 519 |
| A method should have only one exit point, and that should be the last statement in the method | 524 |
| The same String literal appears 4 times in this file; the first occurrence is on line 561 | 561 |
| Avoid unused local variables such as 'indentChange' | 589 |
| A method should have only one exit point, and that should be the last statement in the method | 686 |
| A method should have only one exit point, and that should be the last statement in the method | 690 |
| A method should have only one exit point, and that should be the last statement in the method | 695 |
| A method should have only one exit point, and that should be the last statement in the method | 701 |
| Avoid unused local variables such as 'retVal' | 719 |
| A method should have only one exit point, and that should be the last statement in the method | 733 |
| A method should have only one exit point, and that should be the last statement in the method | 747 |
| Violation | Line |
|---|---|
| The class 'OWLFormattingStrategy' has a Cyclomatic Complexity of 4 (Highest = 12). | 45 |
| A method should have only one exit point, and that should be the last statement in the method | 133 |
| A method should have only one exit point, and that should be the last statement in the method | 185 |
| A method should have only one exit point, and that should be the last statement in the method | 193 |
| The method 'wrapTags' has a Cyclomatic Complexity of 12. | 226 |
| A method should have only one exit point, and that should be the last statement in the method | 232 |
| A method should have only one exit point, and that should be the last statement in the method | 237 |
| The same String literal appears 7 times in this file; the first occurrence is on line 259 | 259 |
| A method should have only one exit point, and that should be the last statement in the method | 318 |
| A method should have only one exit point, and that should be the last statement in the method | 325 |
| A method should have only one exit point, and that should be the last statement in the method | 348 |
| A method should have only one exit point, and that should be the last statement in the method | 353 |
| A method should have only one exit point, and that should be the last statement in the method | 357 |
| A method should have only one exit point, and that should be the last statement in the method | 377 |
| A method should have only one exit point, and that should be the last statement in the method | 389 |
| A method should have only one exit point, and that should be the last statement in the method | 393 |
| Avoid reassigning parameters such as 'indent' | 427 |
| Avoid reassigning parameters such as 'length' | 427 |
| Avoid reassigning parameters such as 'offset' | 427 |
| A method should have only one exit point, and that should be the last statement in the method | 444 |
| A method should have only one exit point, and that should be the last statement in the method | 469 |
| Violation | Line |
|---|---|
| Avoid assigments in operands | 57 |
| A method should have only one exit point, and that should be the last statement in the method | 77 |
| A method should have only one exit point, and that should be the last statement in the method | 106 |
| 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 | 115 |
| Violation | Line |
|---|---|
| Avoid unused private fields such as '_bTagFound' | 28 |
| Violation | Line |
|---|---|
| Avoid unused private methods such as 'makeToken' | 39 |
| All methods are static. Consider using Singleton instead. | 66 |
| Violation | Line |
|---|---|
| Avoid assigments in operands | 38 |
| A method should have only one exit point, and that should be the last statement in the method | 43 |
| Violation | Line |
|---|---|
| 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 | 50 |
| A method should have only one exit point, and that should be the last statement in the method | 53 |
| A method should have only one exit point, and that should be the last statement in the method | 58 |
| 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 | 60 |
| Violation | Line |
|---|---|
| The class 'CombinationDialogCellEditor' has a Cyclomatic Complexity of 6 (Highest = 10). | 46 |
| The method 'openDialogBox' has a Cyclomatic Complexity of 10. | 83 |
| Avoid unused local variables such as 'result' | 87 |
| Deeply nested if..then statements are hard to read | 143 |
| Violation | Line |
|---|---|
| Avoid unused imports such as 'ComboBoxCellEditor' | 16 |
| Avoid using implementation types like 'HashMap'; use the interface instead | 39 |
| Avoid using implementation types like 'HashMap'; use the interface instead | 40 |
| Avoid calls to overridable methods during construction | 65 |
| Violation | Line |
|---|---|
| Avoid unused private fields such as '_restriction' | 60 |
| Avoid empty 'if' statements | 203 |
| Avoid really long methods. | 318 |
| A high number of imports can indicate a high degree of coupling within an object. | 557 |
| A value of 29 may denote a high amount of coupling within the class | 557 |
| Violation | Line |
|---|---|
| Avoid using implementation types like 'HashMap'; use the interface instead | 35 |
| Avoid using implementation types like 'HashMap'; use the interface instead | 39 |
| Avoid calls to overridable methods during construction | 56 |
| Violation | Line |
|---|---|
| Avoid really long methods. | 120 |
| Avoid empty catch blocks | 168 |
| Avoid empty catch blocks | 215 |
| Violation | Line |
|---|---|
| Avoid really long Classes. | 61 |
| The class 'RestrictionEditorInspector' has a Cyclomatic Complexity of 4 (Highest = 11). | 61 |
| Avoid unused private fields such as '_restrictionsCache' | 68 |
| The same String literal appears 4 times in this file; the first occurrence is on line 99 | 99 |
| Avoid unused local variables such as 'i' | 102 |
| The method 'getObjectFromRestriction' has a Cyclomatic Complexity of 11. | 134 |
| Assigning an Object to null is a code smell. Consider refactoring. | 159 |
| Deeply nested if..then statements are hard to read | 171 |
| Deeply nested if..then statements are hard to read | 298 |
| Avoid unused local variables such as 'node' | 340 |
| Avoid really long methods. | 507 |
| Avoid unused local variables such as 'node' | 512 |
| Assigning an Object to null is a code smell. Consider refactoring. | 553 |
| Avoid empty catch blocks | 623 |
| Avoid unused local variables such as 'model' | 699 |
| The class 'NamespaceModelSynchronizer' has a Cyclomatic Complexity of 6 (Highest = 14). | 766 |
| Avoid using implementation types like 'HashSet'; use the interface instead | 775 |
| Avoid using implementation types like 'HashSet'; use the interface instead | 781 |
| Assigning an Object to null is a code smell. Consider refactoring. | 827 |
| Avoid empty catch blocks | 847 |
| Avoid really long methods. | 886 |
| The method 'load' has a Cyclomatic Complexity of 14. | 886 |
| The method 'oastChanged' has a Cyclomatic Complexity of 10. | 1036 |
| Avoid unused local variables such as 'namespaceDeltas' | 1039 |
| Assigning an Object to null is a code smell. Consider refactoring. | 1072 |
| A high number of imports can indicate a high degree of coupling within an object. | 1100 |
| A value of 40 may denote a high amount of coupling within the class | 1100 |
| Violation | Line |
|---|---|
| Assigning an Object to null is a code smell. Consider refactoring. | 230 |
| Avoid unused local variables such as 'klass' | 365 |
| Assigning an Object to null is a code smell. Consider refactoring. | 407 |
| The class 'JenaLabelProvider' has a Cyclomatic Complexity of 4 (Highest = 11). | 484 |
| The method 'getColumnText' has a Cyclomatic Complexity of 11. | 545 |
| Avoid unused local variables such as 'qj' | 615 |
| Violation | Line |
|---|---|
| The class 'RestrictionEditorTableTree' has a Cyclomatic Complexity of 3 (Highest = 13). | 61 |
| Avoid really long methods. | 163 |
| The method 'createButtons' has a Cyclomatic Complexity of 13. | 163 |
| Avoid empty catch blocks | 193 |
| Deeply nested if..then statements are hard to read | 201 |
| Avoid empty catch blocks | 213 |
| The class 'InternalCellModifier' has a Cyclomatic Complexity of 6 (Highest = 10). | 433 |
| Avoid unused local variables such as 'children' | 438 |
| Avoid unused local variables such as 'i' | 440 |
| Avoid reassigning parameters such as 'element' | 529 |
| The method 'modify' has a Cyclomatic Complexity of 10. | 529 |
| Avoid unused local variables such as 'model' | 532 |
| A high number of imports can indicate a high degree of coupling within an object. | 619 |
| A value of 31 may denote a high amount of coupling within the class | 619 |
| Violation | Line |
|---|---|
| The class 'RestrictionEditorTree' has a Cyclomatic Complexity of 3 (Highest = 13). | 61 |
| Avoid really long methods. | 163 |
| The method 'createButtons' has a Cyclomatic Complexity of 13. | 163 |
| Avoid empty catch blocks | 193 |
| Deeply nested if..then statements are hard to read | 201 |
| Avoid empty catch blocks | 213 |
| The class 'InternalCellModifier' has a Cyclomatic Complexity of 6 (Highest = 10). | 433 |
| Avoid unused local variables such as 'children' | 438 |
| Avoid unused local variables such as 'i' | 440 |
| Avoid reassigning parameters such as 'element' | 529 |
| The method 'modify' has a Cyclomatic Complexity of 10. | 529 |
| Avoid unused local variables such as 'model' | 532 |
| A high number of imports can indicate a high degree of coupling within an object. | 619 |
| A value of 31 may denote a high amount of coupling within the class | 619 |
| Violation | Line |
|---|---|
| A value of 23 may denote a high amount of coupling within the class | 769 |
| Violation | Line |
|---|---|
| The class 'DumpOntContentProvider' has a Cyclomatic Complexity of 4 (Highest = 10). | 26 |
| The method 'getChildren' has a Cyclomatic Complexity of 10. | 57 |
| 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 | 77 |
| A method should have only one exit point, and that should be the last statement in the method | 91 |
| 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 | 101 |
| A method should have only one exit point, and that should be the last statement in the method | 114 |
| A method should have only one exit point, and that should be the last statement in the method | 122 |
| A method should have only one exit point, and that should be the last statement in the method | 131 |
| 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 | 148 |
| 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 | 157 |
| A method should have only one exit point, and that should be the last statement in the method | 162 |
| Violation | Line |
|---|---|
| A method should have only one exit point, and that should be the last statement in the method | 32 |
| 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 | 48 |
| A method should have only one exit point, and that should be the last statement in the method | 53 |
| Violation | Line |
|---|---|
| All methods are static. Consider using Singleton instead. | 54 |
| Violation | Line |
|---|---|
| The class 'InterfaceGenerator' has a Cyclomatic Complexity of 4 (Highest = 13). | 66 |
| Avoid really long methods. | 93 |
| The method 'performGeneration' has a Cyclomatic Complexity of 13. | 93 |
| Avoid unused local variables such as 'model' | 99 |
| Avoid unused local variables such as 'sBase' | 100 |
| Avoid unused local variables such as 'sUri' | 119 |
| Avoid unused local variables such as 'root' | 157 |
| A method should have only one exit point, and that should be the last statement in the method | 246 |
| A method should have only one exit point, and that should be the last statement in the method | 322 |
| Avoid unused formal parameters such as 'document' | 380 |
| Avoid unused local variables such as 'md' | 409 |
| A high number of imports can indicate a high degree of coupling within an object. | 412 |
| A value of 31 may denote a high amount of coupling within the class | 412 |
| Violation | Line |
|---|---|
| A method should have only one exit point, and that should be the last statement in the method | 128 |
| Avoid unused local variables such as 'url' | 166 |
| All methods are static. Consider using Singleton instead. | 199 |
| Violation | Line |
|---|---|
| A method should have only one exit point, and that should be the last statement in the method | 88 |
| A method should have only one exit point, and that should be the last statement in the method | 115 |
| Avoid unused local variables such as 'res' | 161 |
| A method should have only one exit point, and that should be the last statement in the method | 173 |
| Violation | Line |
|---|---|
| The class 'VocabularyGenerator' has a Cyclomatic Complexity of 7 (Highest = 12). | 47 |
| Avoid really long methods. | 74 |
| The method 'performGeneration' has a Cyclomatic Complexity of 12. | 74 |
| Avoid unused local variables such as 'model' | 79 |
| Violation | Line |
|---|---|
| Avoid really long methods. | 75 |
| Assigning an Object to null is a code smell. Consider refactoring. | 118 |
| Violation | Line |
|---|---|
| Assigning an Object to null is a code smell. Consider refactoring. | 83 |
| Violation | Line |
|---|---|
| Avoid really long Classes. | 84 |
| The class 'SemanticWebTranslatorWizardHelper' has a Cyclomatic Complexity of 3 (Highest = 12). | 84 |
| Avoid unused private fields such as 'OKAY' | 92 |
| Avoid unused private fields such as 'ERROR' | 94 |
| Avoid unused private fields such as 'WARNING' | 96 |
| Avoid unused private fields such as '_currentPage' | 104 |
| Avoid unused local variables such as 'toReturn' | 212 |
| Avoid unused local variables such as 'newParent' | 214 |
| Avoid unused local variables such as 'glayout' | 353 |
| Avoid unused local variables such as 'toReturn' | 728 |
| Avoid unused local variables such as 'newParent' | 730 |
| Avoid unused local variables such as 'target' | 761 |
| Ensure you override both equals() and hashCode() | 1869 |
| The constructor 'SemanticWebTranslatorWizardHelper' has a Cyclomatic Complexity of 12. | 2004 |
| Avoid empty catch blocks | 2164 |
| Avoid unused local variables such as 'status' | 2180 |
| A high number of imports can indicate a high degree of coupling within an object. | 2234 |
| A value of 48 may denote a high amount of coupling within the class | 2234 |
| Violation | Line |
|---|---|
| The class 'TranslateAction' has a Cyclomatic Complexity of 5 (Highest = 13). | 35 |
| Avoid unnecessary constructors - the compiler will generate these for you | 46 |
| The method 'selectionChanged' has a Cyclomatic Complexity of 13. | 86 |
| Avoid unused local variables such as 'extension' | 95 |
| Assigning an Object to null is a code smell. Consider refactoring. | 97 |
| Assigning an Object to null is a code smell. Consider refactoring. | 115 |
| Deeply nested if..then statements are hard to read | 120 |
| Deeply nested if..then statements are hard to read | 124 |
| Deeply nested if..then statements are hard to read | 145 |
| Deeply nested if..then statements are hard to read | 151 |
| Violation | Line |
|---|---|
| Assigning an Object to null is a code smell. Consider refactoring. | 63 |
| Assigning an Object to null is a code smell. Consider refactoring. | 64 |
| Assigning an Object to null is a code smell. Consider refactoring. | 130 |
| Assigning an Object to null is a code smell. Consider refactoring. | 131 |
| Violation | Line |
|---|---|
| Avoid unused private fields such as 'ID_STR' | 30 |
| Avoid unused private fields such as 'TOOLTIP_STR' | 31 |
| Assigning an Object to null is a code smell. Consider refactoring. | 51 |
| Violation | Line |
|---|---|
| Avoid unused local variables such as 'tempTranslator' | 59 |
| Violation | Line |
|---|---|
| The class 'LibrariesPreferencesPage' has a Cyclomatic Complexity of 5 (Highest = 14). | 55 |
| Avoid really long methods. | 69 |
| The method 'createContents' has a Cyclomatic Complexity of 14. | 69 |
| Deeply nested if..then statements are hard to read | 183 |
| A high number of imports can indicate a high degree of coupling within an object. | 350 |
| A value of 21 may denote a high amount of coupling within the class | 350 |
| Violation | Line |
|---|---|
| A method should have only one exit point, and that should be the last statement in the method | 37 |
| 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 | 75 |
| A method should have only one exit point, and that should be the last statement in the method | 79 |
| A method should have only one exit point, and that should be the last statement in the method | 92 |
| Violation | Line |
|---|---|
| A method should have only one exit point, and that should be the last statement in the method | 42 |
| A method should have only one exit point, and that should be the last statement in the method | 48 |
| A method should have only one exit point, and that should be the last statement in the method | 52 |
| 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 | 60 |
| A method should have only one exit point, and that should be the last statement in the method | 64 |
| Avoid unused local variables such as 'iterator' | 76 |
| A method should have only one exit point, and that should be the last statement in the method | 79 |
| Violation | Line |
|---|---|
| A method should have only one exit point, and that should be the last statement in the method | 52 |
| 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 | 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 | 70 |
| A method should have only one exit point, and that should be the last statement in the method | 74 |
| A method should have only one exit point, and that should be the last statement in the method | 78 |
| A method should have only one exit point, and that should be the last statement in the method | 82 |
| Violation | Line |
|---|---|
| A method should have only one exit point, and that should be the last statement in the method | 37 |
| A method should have only one exit point, and that should be the last statement in the method | 41 |
| 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 |
| Violation | Line |
|---|---|
| All methods are static. Consider using Singleton instead. | 54 |
| Violation | Line |
|---|---|
| The class 'OWLActionProcessor' has a Cyclomatic Complexity of 4 (Highest = 18). | 52 |
| A method should have only one exit point, and that should be the last statement in the method | 65 |
| Avoid unused local variables such as 'obj' | 77 |
| Avoid really long methods. | 104 |
| The method 'validateDocument' has a Cyclomatic Complexity of 18. | 104 |
| Avoid really long methods. | 108 |
| The method 'execute' has a Cyclomatic Complexity of 15. | 108 |
| Avoid unused local variables such as 'prefs' | 113 |
| Avoid unused local variables such as 'vMarkers' | 161 |
| A high number of imports can indicate a high degree of coupling within an object. | 347 |
| A value of 26 may denote a high amount of coupling within the class | 347 |
| Violation | Line |
|---|---|
| Avoid unused private methods such as 'addSeparator' | 77 |
| Avoid unused private methods such as 'createDefaultComposite' | 160 |
| Assigning an Object to null is a code smell. Consider refactoring. | 200 |
| Avoid unused local variables such as 'ild' | 263 |
| Avoid unused local variables such as 'i' | 264 |
| Avoid unused local variables such as 'ild' | 299 |
| Avoid unused local variables such as 'i' | 300 |
| A high number of imports can indicate a high degree of coupling within an object. | 355 |
| Violation | Line |
|---|---|
| Avoid unused local variables such as 'sdf' | 70 |
| Avoid assigments in operands | 88 |
| Avoid empty catch blocks | 100 |
| Avoid empty catch blocks | 110 |
| Avoid empty catch blocks | 134 |
| Avoid empty catch blocks | 161 |
| Violation | Line |
|---|---|
| Avoid unused local variables such as 'tempEntry' | 317 |
| Avoid unused local variables such as 'i' | 318 |
| Avoid unused local variables such as 'tempEntry' | 337 |
| Avoid unused local variables such as 'i' | 338 |
| Ensure you override both equals() and hashCode() | 350 |
| Violation | Line |
|---|---|
| Avoid unused local variables such as 'name' | 123 |
| Violation | Line |
|---|---|
| Avoid unused formal parameters such as 'left' | 156 |
| Avoid unused formal parameters such as 'right' | 156 |
| Assigning an Object to null is a code smell. Consider refactoring. | 183 |
| Avoid assigments in operands | 188 |
| Assigning an Object to null is a code smell. Consider refactoring. | 191 |
| 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 | 228 |
| A method should have only one exit point, and that should be the last statement in the method | 235 |
| Violation | Line |
|---|---|
| Avoid unused local variables such as 'input' | 110 |
| A method should have only one exit point, and that should be the last statement in the method | 115 |
| 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 | 174 |
| 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 | 214 |
| Avoid assigments in operands | 222 |
| 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 |
| Violation | Line |
|---|---|
| The class 'NewOWLDocumentWizardPage' has a Cyclomatic Complexity of 3 (Highest = 12). | 83 |
| Avoid unused private fields such as 'INITIAL_OWL_CONTENT_ENTITIES' | 89 |
| Avoid unused private fields such as '_bFirstImportCheck' | 127 |
| Assigning an Object to null is a code smell. Consider refactoring. | 245 |
| Avoid empty catch blocks | 309 |
| Avoid reassigning parameters such as 'contents' | 327 |
| A method should have only one exit point, and that should be the last statement in the method | 440 |
| A method should have only one exit point, and that should be the last statement in the method | 482 |
| A method should have only one exit point, and that should be the last statement in the method | 507 |
| A method should have only one exit point, and that should be the last statement in the method | 536 |
| A method should have only one exit point, and that should be the last statement in the method | 593 |
| Avoid reassigning parameters such as 'input' | 597 |
| A method should have only one exit point, and that should be the last statement in the method | 601 |
| A method should have only one exit point, and that should be the last statement in the method | 614 |
| A method should have only one exit point, and that should be the last statement in the method | 642 |
| Avoid really long methods. | 740 |
| The method 'validatePage' has a Cyclomatic Complexity of 12. | 740 |
| A method should have only one exit point, and that should be the last statement in the method | 771 |
| A method should have only one exit point, and that should be the last statement in the method | 784 |
| Assigning an Object to null is a code smell. Consider refactoring. | 809 |
| A method should have only one exit point, and that should be the last statement in the method | 818 |
| A method should have only one exit point, and that should be the last statement in the method | 838 |
| A high number of imports can indicate a high degree of coupling within an object. | 884 |
| A value of 33 may denote a high amount of coupling within the class | 884 |
| Violation | Line |
|---|---|
| Avoid unnecessary constructors - the compiler will generate these for you | 41 |
| Avoid empty 'if' statements | 75 |
| Violation | Line |
|---|---|
| Avoid unused formal parameters such as 'left' | 179 |
| Avoid unused formal parameters such as 'right' | 179 |
| Assigning an Object to null is a code smell. Consider refactoring. | 206 |
| A method should have only one exit point, and that should be the last statement in the method | 214 |
| Avoid assigments in operands | 218 |
| Assigning an Object to null is a code smell. Consider refactoring. | 223 |
| A method should have only one exit point, and that should be the last statement in the method | 230 |
| Avoid assigments in operands | 234 |
| Assigning an Object to null is a code smell. Consider refactoring. | 239 |
| Avoid unused formal parameters such as 'email' | 266 |
| Avoid unused formal parameters such as 'date' | 270 |
| Violation | Line |
|---|---|
| A method should have only one exit point, and that should be the last statement in the method | 134 |
| Assigning an Object to null is a code smell. Consider refactoring. | 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 | 181 |
| Violation | Line |
|---|---|
| Avoid unnecessary constructors - the compiler will generate these for you | 41 |
| Avoid empty 'if' statements | 94 |
| Violation | Line |
|---|---|
| Avoid unused formal parameters such as 'left' | 191 |
| Avoid unused formal parameters such as 'right' | 191 |
| Assigning an Object to null is a code smell. Consider refactoring. | 218 |
| Avoid assigments in operands | 223 |
| Assigning an Object to null is a code smell. Consider refactoring. | 226 |
| 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 | 264 |
| A method should have only one exit point, and that should be the last statement in the method | 271 |
| Violation | Line |
|---|---|
| Avoid unused local variables such as 'oldLibraryFile' | 259 |
| A value of 21 may denote a high amount of coupling within the class | 316 |
| Violation | Line |
|---|---|
| The class 'OWLLibraryBuilderPageOne' has a Cyclomatic Complexity of 3 (Highest = 13). | 49 |
| Avoid really long methods. | 181 |
| The method 'createURLResourcesGroup' has a Cyclomatic Complexity of 13. | 181 |
| Avoid unused local variables such as 'currentName' | 230 |
| A high number of imports can indicate a high degree of coupling within an object. | 441 |
| A value of 24 may denote a high amount of coupling within the class | 441 |
| Violation | Line |
|---|---|
| Avoid unused private fields such as '_nameText' | 30 |
| Violation | Line |
|---|---|
| Avoid really long methods. | 122 |
| Avoid unused local variables such as 'lrd' | 260 |
| Assigning an Object to null is a code smell. Consider refactoring. | 299 |
| Avoid unused local variables such as 'lrd' | 336 |
| Violation | Line |
|---|---|
| Assigning an Object to null is a code smell. Consider refactoring. | 66 |
| Violation | Line |
|---|---|
| Avoid unused private fields such as '_workbench' | 63 |
| Avoid unused local variables such as 'string' | 311 |
| A high number of imports can indicate a high degree of coupling within an object. | 381 |
| A value of 25 may denote a high amount of coupling within the class | 381 |
| Violation | Line |
|---|---|
| Avoid unnecessary constructors - the compiler will generate these for you | 49 |
| Avoid unused local variables such as 'tempProperty' | 160 |
| Violation | Line |
|---|---|
| Avoid unused private fields such as '_editor' | 70 |
| A high number of imports can indicate a high degree of coupling within an object. | 531 |
| A value of 22 may denote a high amount of coupling within the class | 531 |
| Violation | Line |
|---|---|
| All methods are static. Consider using Singleton instead. | 58 |
| Violation | Line |
|---|---|
| Assigning an Object to null is a code smell. Consider refactoring. | 103 |
| 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 | 144 |
| 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 | 195 |
| A method should have only one exit point, and that should be the last statement in the method | 209 |
| A method should have only one exit point, and that should be the last statement in the method | 213 |
| A method should have only one exit point, and that should be the last statement in the method | 258 |
| A method should have only one exit point, and that should be the last statement in the method | 307 |
| A method should have only one exit point, and that should be the last statement in the method | 320 |
| A method should have only one exit point, and that should be the last statement in the method | 322 |
| Violation | Line |
|---|---|
| All methods are static. Consider using Singleton instead. | 58 |
| Violation | Line |
|---|---|
| The class 'URIExplorerContentProvider' has a Cyclomatic Complexity of 4 (Highest = 12). | 43 |
| The method 'getChildren' has a Cyclomatic Complexity of 12. | 52 |
| 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 | 89 |
| A method should have only one exit point, and that should be the last statement in the method | 95 |
| Avoid unused local variables such as 'numAnon' | 111 |
| Deeply nested if..then statements are hard to read | 124 |
| A method should have only one exit point, and that should be the last statement in the method | 131 |
| 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 | 141 |
| Avoid empty catch blocks | 146 |
| A method should have only one exit point, and that should be the last statement in the method | 159 |
| A method should have only one exit point, and that should be the last statement in the method | 163 |
| 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 | 186 |
| 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 | 255 |
| A method should have only one exit point, and that should be the last statement in the method | 301 |
| A method should have only one exit point, and that should be the last statement in the method | 318 |
| Violation | Line |
|---|---|
| The class 'URIExplorer' has a Cyclomatic Complexity of 4 (Highest = 19). | 106 |
| Avoid unused private fields such as '_actionGroup' | 118 |
| Avoid unused private fields such as '_actionPaste' | 121 |
| Avoid unused private fields such as '_actionLibraryRefresh' | 124 |
| Avoid unused local variables such as 'wsroot' | 147 |
| Avoid empty finally blocks | 169 |
| Avoid unused local variables such as 'clipboard' | 183 |
| The method 'doubleClick' has a Cyclomatic Complexity of 11. | 364 |
| Avoid unused local variables such as 'tree' | 432 |
| Avoid really long methods. | 453 |
| The method 'menuAboutToShow' has a Cyclomatic Complexity of 19. | 453 |
| The same String literal appears 4 times in this file; the first occurrence is on line 634 | 634 |
| A method should have only one exit point, and that should be the last statement in the method | 649 |
| Avoid assigments in operands | 749 |
| A high number of imports can indicate a high degree of coupling within an object. | 895 |
| A value of 49 may denote a high amount of coupling within the class | 895 |