|
|
|
|
|
|
|
The following document contains the results of PMD
| Violation | Line |
|---|---|
| Each class should declare at least one constructor | 3 - 26 |
| Violation | Line |
|---|---|
| Use explicit scoping instead of the default package private level | 10 |
| Use explicit scoping instead of the default package private level | 11 |
| Violation | Line |
|---|---|
| Use explicit scoping instead of the default package private level | 6 |
| Violation | Line |
|---|---|
| Use explicit scoping instead of the default package private level | 9 |
| Violation | Line |
|---|---|
| Each class should declare at least one constructor | 8 - 15 |
| Violation | Line |
|---|---|
| A method should have only one exit point, and that should be the last statement in the method | 31 |
| 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 | 51 |
| 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 | 54 |
| A method should have only one exit point, and that should be the last statement in the method | 56 |
| A method should have only one exit point, and that should be the last statement in the method | 59 |
| 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 | 66 |
| A method should have only one exit point, and that should be the last statement in the method | 68 |
| A method should have only one exit point, and that should be the last statement in the method | 70 |
| 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 | 72 |
| 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 | 74 |
| Violation | Line |
|---|---|
| It is a good practice to call super() in a constructor | 17 - 26 |
| Violation | Line |
|---|---|
| Avoid modifiers which are implied by the context | 5 |
| Avoid modifiers which are implied by the context | 7 |
| Violation | Line |
|---|---|
| Use explicit scoping instead of the default package private level | 5 |
| Use explicit scoping instead of the default package private level | 6 |
| Violation | Line |
|---|---|
| Assigning an Object to null is a code smell. Consider refactoring. | 11 |
| Assigning an Object to null is a code smell. Consider refactoring. | 12 |
| Assigning an Object to null is a code smell. Consider refactoring. | 17 |
| Violation | Line |
|---|---|
| Each class should declare at least one constructor | 9 - 26 |
| Each class should declare at least one constructor | 17 - 25 |
| Violation | Line |
|---|---|
| Each class should declare at least one constructor | 4 - 11 |
| Violation | Line |
|---|---|
| Use explicit scoping instead of the default package private level | 11 |
| Use explicit scoping instead of the default package private level | 12 |
| Avoid empty catch blocks | 26 - 27 |
| Violation | Line |
|---|---|
| Use explicit scoping instead of the default package private level | 6 |
| A method should have only one exit point, and that should be the last statement in the method | 13 |
| Violation | Line |
|---|---|
| A method should have only one exit point, and that should be the last statement in the method | 30 |
| 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 | 51 |
| 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 | 55 |
| A method should have only one exit point, and that should be the last statement in the method | 59 |
| 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 | 66 |
| A method should have only one exit point, and that should be the last statement in the method | 68 |
| A method should have only one exit point, and that should be the last statement in the method | 70 |
| 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 | 72 |
| 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 | 74 |
| 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 | 76 |
| Violation | Line |
|---|---|
| It is a good practice to call super() in a constructor | 19 - 33 |
| A method should have only one exit point, and that should be the last statement in the method | 41 |
| Violation | Line |
|---|---|
| Use explicit scoping instead of the default package private level | 9 |
| Use explicit scoping instead of the default package private level | 10 |
| Use explicit scoping instead of the default package private level | 11 |
| It is a good practice to call super() in a constructor | 13 - 18 |
| Violation | Line |
|---|---|
| Each class should declare at least one constructor | 4 - 13 |
| Violation | Line |
|---|---|
| Avoid modifiers which are implied by the context | 5 |
| Avoid modifiers which are implied by the context | 7 |
| Avoid modifiers which are implied by the context | 9 |
| Violation | Line |
|---|---|
| Use explicit scoping instead of the default package private level | 7 |
| Violation | Line |
|---|---|
| Perhaps 'transport' could be replaced by a local variable. | 9 |
| Violation | Line |
|---|---|
| Avoid modifiers which are implied by the context | 9 |
| Avoid modifiers which are implied by the context | 11 |
| Violation | Line |
|---|---|
| Avoid modifiers which are implied by the context | 5 |
| Violation | Line |
|---|---|
| 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 | 80 |
| Violation | Line |
|---|---|
| Use explicit scoping instead of the default package private level | 8 |
| Use explicit scoping instead of the default package private level | 9 |
| It is a good practice to call super() in a constructor | 11 - 14 |
| Violation | Line |
|---|---|
| Each class should declare at least one constructor | 27 - 34 |
| Violation | Line |
|---|---|
| Avoid modifiers which are implied by the context | 10 |
| Violation | Line |
|---|---|
| Perhaps 'count' could be replaced by a local variable. | 17 |
| A method should have only one exit point, and that should be the last statement in the method | 56 |
| Violation | Line |
|---|---|
| Each class should declare at least one constructor | 15 - 114 |
| Use explicit scoping instead of the default package private level | 17 |
| A method should have only one exit point, and that should be the last statement in the method | 24 |
| 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 | 37 |
| A method should have only one exit point, and that should be the last statement in the method | 38 |
| A method should have only one exit point, and that should be the last statement in the method | 43 |
| 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 | 49 |
| 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 | 59 |
| A method should have only one exit point, and that should be the last statement in the method | 66 |
| Violation | Line |
|---|---|
| Each class should declare at least one constructor | 18 - 122 |
| 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 | 71 |
| Violation | Line |
|---|---|
| Each class should declare at least one constructor | 78 - 549 |
| Use explicit scoping instead of the default package private level | 92 |
| Use explicit scoping instead of the default package private level | 93 |
| 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 | 355 |
| A method should have only one exit point, and that should be the last statement in the method | 381 |
| Violation | Line |
|---|---|
| Use explicit scoping instead of the default package private level | 60 |
| It is a good practice to call super() in a constructor | 67 - 69 |
| Violation | Line |
|---|---|
| Each class should declare at least one constructor | 50 - 552 |
| A method should have only one exit point, and that should be the last statement in the method | 105 |
| A method should have only one exit point, and that should be the last statement in the method | 106 |
| 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 | 109 |
| A method should have only one exit point, and that should be the last statement in the method | 111 |
| A method should have only one exit point, and that should be the last statement in the method | 113 |
| A method should have only one exit point, and that should be the last statement in the method | 115 |
| 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 | 117 |
| A method should have only one exit point, and that should be the last statement in the method | 118 |
| A method should have only one exit point, and that should be the last statement in the method | 119 |
| Violation | Line |
|---|---|
| Each class should declare at least one constructor | 47 - 554 |
| 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 | 82 |
| Assigning an Object to null is a code smell. Consider refactoring. | 126 |
| A method should have only one exit point, and that should be the last statement in the method | 230 |
| 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 | 249 |
| Assigning an Object to null is a code smell. Consider refactoring. | 311 |
| A method should have only one exit point, and that should be the last statement in the method | 313 |
| A method should have only one exit point, and that should be the last statement in the method | 325 |
| Assigning an Object to null is a code smell. Consider refactoring. | 330 |
| A method should have only one exit point, and that should be the last statement in the method | 332 |
| A method should have only one exit point, and that should be the last statement in the method | 335 |
| Assigning an Object to null is a code smell. Consider refactoring. | 341 |
| A method should have only one exit point, and that should be the last statement in the method | 343 |
| A method should have only one exit point, and that should be the last statement in the method | 346 |
| A method should have only one exit point, and that should be the last statement in the method | 355 |
| A method should have only one exit point, and that should be the last statement in the method | 543 |
| Perhaps 'jjutil' could be replaced by a local variable. | 547 |
| Violation | Line |
|---|---|
| Each class should declare at least one constructor | 9 - 13 |
| Violation | Line |
|---|---|
| Each class should declare at least one constructor | 9 - 137 |
| Violation | Line |
|---|---|
| Each class should declare at least one constructor | 9 - 88 |
| 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 | 76 |
| A method should have only one exit point, and that should be the last statement in the method | 84 |
| 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 | 34 |
| A method should have only one exit point, and that should be the last statement in the method | 38 |
| A method should have only one exit point, and that should be the last statement in the method | 42 |
| Violation | Line |
|---|---|
| Use explicit scoping instead of the default package private level | 32 |
| Use explicit scoping instead of the default package private level | 33 |
| A method should have only one exit point, and that should be the last statement in the method | 51 |
| Violation | Line |
|---|---|
| Avoid modifiers which are implied by the context | 9 |
| Avoid modifiers which are implied by the context | 10 |
| Avoid modifiers which are implied by the context | 11 |
| Violation | Line |
|---|---|
| Avoid unnecessary constructors - the compiler will generate these for you | 6 |
| It is a good practice to call super() in a constructor | 6 |
| Violation | Line |
|---|---|
| Avoid unnecessary constructors - the compiler will generate these for you | 6 |
| It is a good practice to call super() in a constructor | 6 |
| Violation | Line |
|---|---|
| Perhaps 'UK' could be replaced by a local variable. | 21 |
| Perhaps 'cache' could be replaced by a local variable. | 43 |
| Perhaps 'cacheSerial' could be replaced by a local variable. | 44 |
| 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 | 54 |
| A method should have only one exit point, and that should be the last statement in the method | 60 |
| Violation | Line |
|---|---|
| Avoid unnecessary constructors - the compiler will generate these for you | 10 |
| It is a good practice to call super() in a constructor | 10 |
| A method should have only one exit point, and that should be the last statement in the method | 14 |
| A method should have only one exit point, and that should be the last statement in the method | 15 |
| Violation | Line |
|---|---|
| Avoid unnecessary constructors - the compiler will generate these for you | 13 |
| It is a good practice to call super() in a constructor | 13 |
| Violation | Line |
|---|---|
| Avoid unnecessary constructors - the compiler will generate these for you | 6 |
| It is a good practice to call super() in a constructor | 6 |
| Violation | Line |
|---|---|
| Avoid unnecessary constructors - the compiler will generate these for you | 9 - 10 |
| It is a good practice to call super() in a constructor | 9 - 10 |
| A method should have only one exit point, and that should be the last statement in the method | 23 |
| A method should have only one exit point, and that should be the last statement in the method | 34 |
| A method should have only one exit point, and that should be the last statement in the method | 46 |
| Violation | Line |
|---|---|
| Avoid unnecessary constructors - the compiler will generate these for you | 10 |
| It is a good practice to call super() in a constructor | 10 |
| Violation | Line |
|---|---|
| Avoid unnecessary constructors - the compiler will generate these for you | 6 |
| It is a good practice to call super() in a constructor | 6 |
| Violation | Line |
|---|---|
| Use explicit scoping instead of the default package private level | 14 |
| Use explicit scoping instead of the default package private level | 15 |
| Use explicit scoping instead of the default package private level | 16 |
| Use explicit scoping instead of the default package private level | 17 |
| A method should have only one exit point, and that should be the last statement in the method | 37 |
| Violation | Line |
|---|---|
| Avoid unnecessary constructors - the compiler will generate these for you | 6 |
| It is a good practice to call super() in a constructor | 6 |
| Violation | Line |
|---|---|
| Avoid unnecessary constructors - the compiler will generate these for you | 6 |
| It is a good practice to call super() in a constructor | 6 |
| Violation | Line |
|---|---|
| A method should have only one exit point, and that should be the last statement in the method | 23 |
| A method should have only one exit point, and that should be the last statement in the method | 27 |
| Violation | Line |
|---|---|
| Avoid unnecessary constructors - the compiler will generate these for you | 10 |
| It is a good practice to call super() in a constructor | 10 |
| Violation | Line |
|---|---|
| Avoid unnecessary constructors - the compiler will generate these for you | 37 |
| It is a good practice to call super() in a constructor | 37 |
| Violation | Line |
|---|---|
| Avoid unnecessary constructors - the compiler will generate these for you | 13 |
| It is a good practice to call super() in a constructor | 13 |
| A method should have only one exit point, and that should be the last statement in the method | 41 |
| Violation | Line |
|---|---|
| Each class should declare at least one constructor | 5 - 11 |
| Violation | Line |
|---|---|
| Avoid unnecessary constructors - the compiler will generate these for you | 6 |
| It is a good practice to call super() in a constructor | 6 |
| Violation | Line |
|---|---|
| Avoid unnecessary constructors - the compiler will generate these for you | 30 - 31 |
| It is a good practice to call super() in a constructor | 30 - 31 |
| A method should have only one exit point, and that should be the last statement in the method | 35 |
| 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 | 49 |
| 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 | 60 |
| A method should have only one exit point, and that should be the last statement in the method | 72 |
| Assigning an Object to null is a code smell. Consider refactoring. | 114 |
| Assigning an Object to null is a code smell. Consider refactoring. | 115 |
| Assigning an Object to null is a code smell. Consider refactoring. | 116 |
| Assigning an Object to null is a code smell. Consider refactoring. | 117 |
| Assigning an Object to null is a code smell. Consider refactoring. | 118 |
| Assigning an Object to null is a code smell. Consider refactoring. | 119 |
| Assigning an Object to null is a code smell. Consider refactoring. | 120 |
| Assigning an Object to null is a code smell. Consider refactoring. | 121 |
| Assigning an Object to null is a code smell. Consider refactoring. | 122 |
| It is a good practice to call super() in a constructor | 303 - 306 |
| A method should have only one exit point, and that should be the last statement in the method | 310 |
| A method should have only one exit point, and that should be the last statement in the method | 337 |
| Violation | Line |
|---|---|
| Avoid unnecessary constructors - the compiler will generate these for you | 6 |
| It is a good practice to call super() in a constructor | 6 |
| Violation | Line |
|---|---|
| Avoid unnecessary constructors - the compiler will generate these for you | 9 - 10 |
| It is a good practice to call super() in a constructor | 9 - 10 |
| Violation | Line |
|---|---|
| Avoid unnecessary constructors - the compiler will generate these for you | 6 |
| It is a good practice to call super() in a constructor | 6 |
| Violation | Line |
|---|---|
| Avoid unnecessary constructors - the compiler will generate these for you | 6 |
| It is a good practice to call super() in a constructor | 6 |
| Violation | Line |
|---|---|
| Avoid unnecessary constructors - the compiler will generate these for you | 16 - 17 |
| It is a good practice to call super() in a constructor | 16 - 17 |
| A method should have only one exit point, and that should be the last statement in the method | 31 |
| A method should have only one exit point, and that should be the last statement in the method | 38 |
| A method should have only one exit point, and that should be the last statement in the method | 46 |
| A method should have only one exit point, and that should be the last statement in the method | 49 |
| A method should have only one exit point, and that should be the last statement in the method | 67 |
| Violation | Line |
|---|---|
| Avoid unnecessary constructors - the compiler will generate these for you | 6 |
| It is a good practice to call super() in a constructor | 6 |
| Violation | Line |
|---|---|
| Each class should declare at least one constructor | 9 - 91 |
| Violation | Line |
|---|---|
| Avoid unnecessary constructors - the compiler will generate these for you | 6 |
| It is a good practice to call super() in a constructor | 6 |
| Violation | Line |
|---|---|
| Avoid unnecessary constructors - the compiler will generate these for you | 37 |
| It is a good practice to call super() in a constructor | 37 |
| Violation | Line |
|---|---|
| A method should have only one exit point, and that should be the last statement in the method | 24 |
| A method should have only one exit point, and that should be the last statement in the method | 28 |
| Violation | Line |
|---|---|
| Each class should declare at least one constructor | 59 - 73 |
| Violation | Line |
|---|---|
| Each class should declare at least one constructor | 19 - 98 |
| 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 | 87 |
| A method should have only one exit point, and that should be the last statement in the method | 90 |
| A method should have only one exit point, and that should be the last statement in the method | 93 |
| Violation | Line |
|---|---|
| It is a good practice to call super() in a constructor | 81 - 85 |
| It is a good practice to call super() in a constructor | 97 - 103 |
| Violation | Line |
|---|---|
| Avoid unnecessary constructors - the compiler will generate these for you | 7 - 8 |
| Violation | Line |
|---|---|
| Assigning an Object to null is a code smell. Consider refactoring. | 14 |
| Assigning an Object to null is a code smell. Consider refactoring. | 20 |
| Assigning an Object to null is a code smell. Consider refactoring. | 25 |
| Assigning an Object to null is a code smell. Consider refactoring. | 26 |
| A method should have only one exit point, and that should be the last statement in the method | 30 |
| A method should have only one exit point, and that should be the last statement in the method | 40 |
| Violation | Line |
|---|---|
| Each class should declare at least one constructor | 32 - 264 |
| It is a good practice to call super() in a constructor | 88 - 90 |
| Violation | Line |
|---|---|
| Each class should declare at least one constructor | 25 - 88 |
| A method should have only one exit point, and that should be the last statement in the method | 40 |
| A method should have only one exit point, and that should be the last statement in the method | 83 |
| Violation | Line |
|---|---|
| Perhaps 'whereClause' could be replaced by a local variable. | 11 |
| Violation | Line |
|---|---|
| Each class should declare at least one constructor | 18 - 45 |
| Violation | Line |
|---|---|
| Each class should declare at least one constructor | 27 - 202 |
| Violation | Line |
|---|---|
| Use explicit scoping instead of the default package private level | 8 |
| Use explicit scoping instead of the default package private level | 9 |
| A method should have only one exit point, and that should be the last statement in the method | 19 |
| A method should have only one exit point, and that should be the last statement in the method | 25 |
| Assigning an Object to null is a code smell. Consider refactoring. | 32 |
| Assigning an Object to null is a code smell. Consider refactoring. | 33 |
| Violation | Line |
|---|---|
| Use explicit scoping instead of the default package private level | 18 |
| 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 | 171 |
| Violation | Line |
|---|---|
| Use explicit scoping instead of the default package private level | 10 |
| Violation | Line |
|---|---|
| Avoid modifiers which are implied by the context | 6 |
| Avoid modifiers which are implied by the context | 7 |
| Violation | Line |
|---|---|
| Assigning an Object to null is a code smell. Consider refactoring. | 16 |
| Assigning an Object to null is a code smell. Consider refactoring. | 23 |
| Assigning an Object to null is a code smell. Consider refactoring. | 24 |
| Assigning an Object to null is a code smell. Consider refactoring. | 30 |
| A method should have only one exit point, and that should be the last statement in the method | 38 |
| A method should have only one exit point, and that should be the last statement in the method | 39 |
| 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 | 52 |
| Violation | Line |
|---|---|
| Each class should declare at least one constructor | 30 - 142 |
| Violation | Line |
|---|---|
| Each class should declare at least one constructor | 12 - 34 |
| Violation | Line |
|---|---|
| A method should have only one exit point, and that should be the last statement in the method | 27 |
| A method should have only one exit point, and that should be the last statement in the method | 30 |
| An empty statement (semicolon) not part of a loop | 33 |
| Violation | Line |
|---|---|
| Each class should declare at least one constructor | 26 - 218 |
| Perhaps 'db' could be replaced by a local variable. | 31 |
| Avoid empty catch blocks | 83 |
| Avoid empty catch blocks | 149 - 150 |
| A method should have only one exit point, and that should be the last statement in the method | 184 |
| Assigning an Object to null is a code smell. Consider refactoring. | 194 |
| Avoid empty catch blocks | 198 - 199 |
| A method should have only one exit point, and that should be the last statement in the method | 208 |
| A method should have only one exit point, and that should be the last statement in the method | 214 |
| Violation | Line |
|---|---|
| Perhaps 'db' could be replaced by a local variable. | 10 |
| Violation | Line |
|---|---|
| Each class should declare at least one constructor | 22 - 120 |
| Avoid instantiating Boolean objects; you can usually invoke Boolean.TRUE instead. | 78 |
| It is a good practice to call super() in a constructor | 96 - 99 |
| Assigning an Object to null is a code smell. Consider refactoring. | 97 |
| Assigning an Object to null is a code smell. Consider refactoring. | 98 |
| It is a good practice to call super() in a constructor | 101 - 104 |
| Assigning an Object to null is a code smell. Consider refactoring. | 103 |
| It is a good practice to call super() in a constructor | 106 - 109 |
| Violation | Line |
|---|---|
| Each class should declare at least one constructor | 13 - 57 |
| Violation | Line |
|---|---|
| Each class should declare at least one constructor | 7 - 15 |
| Violation | Line |
|---|---|
| Assigning an Object to null is a code smell. Consider refactoring. | 14 |
| Assigning an Object to null is a code smell. Consider refactoring. | 20 |
| Assigning an Object to null is a code smell. Consider refactoring. | 25 |
| Assigning an Object to null is a code smell. Consider refactoring. | 26 |
| A method should have only one exit point, and that should be the last statement in the method | 30 |
| A method should have only one exit point, and that should be the last statement in the method | 41 |
| Violation | Line |
|---|---|
| Each class should declare at least one constructor | 53 - 69 |
| Use explicit scoping instead of the default package private level | 57 |
| Violation | Line |
|---|---|
| Each class should declare at least one constructor | 10 - 32 |
| A method should have only one exit point, and that should be the last statement in the method | 22 |
| Violation | Line |
|---|---|
| Each class should declare at least one constructor | 11 - 28 |
| Violation | Line |
|---|---|
| Each class should declare at least one constructor | 16 - 67 |
| Violation | Line |
|---|---|
| Each class should declare at least one constructor | 11 - 43 |
| Violation | Line |
|---|---|
| Use explicit scoping instead of the default package private level | 37 |
| 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 | 169 |
| A method should have only one exit point, and that should be the last statement in the method | 177 |
| Violation | Line |
|---|---|
| Use explicit scoping instead of the default package private level | 17 |
| Violation | Line |
|---|---|
| Use explicit scoping instead of the default package private level | 17 |
