PMD Results
The following document contains the results of PMD 6.55.0.
Violations By Priority
Priority 1
org/apache/commons/codec/binary/BaseNCodec.java
Rule |
Violation |
Line |
FieldNamingConventions |
The final field name 'PAD' doesn't match '[a-z][a-zA-Z0-9]*' |
381 |
Priority 3
org/apache/commons/codec/CharEncoding.java
Rule |
Violation |
Line |
UnnecessaryConstructor |
Avoid unnecessary constructors - the compiler will generate these for you |
128–130 |
org/apache/commons/codec/Charsets.java
Rule |
Violation |
Line |
UnnecessaryConstructor |
Avoid unnecessary constructors - the compiler will generate these for you |
169–171 |
org/apache/commons/codec/DecoderException.java
Rule |
Violation |
Line |
CallSuperInConstructor |
It is a good practice to call super() in a constructor |
39–40 |
org/apache/commons/codec/EncoderException.java
Rule |
Violation |
Line |
CallSuperInConstructor |
It is a good practice to call super() in a constructor |
40–41 |
org/apache/commons/codec/Resources.java
Rule |
Violation |
Line |
UnnecessaryConstructor |
Avoid unnecessary constructors - the compiler will generate these for you |
49–51 |
org/apache/commons/codec/StringEncoderComparator.java
Rule |
Violation |
Line |
ShortVariable |
Avoid variables with short names like o1 |
73 |
ShortVariable |
Avoid variables with short names like o2 |
73 |
ShortVariable |
Avoid variables with short names like s1 |
80 |
ShortVariable |
Avoid variables with short names like s2 |
81 |
org/apache/commons/codec/binary/Base16.java
Rule |
Violation |
Line |
LongVariable |
Avoid excessively long variable names like BITS_PER_ENCODED_BYTE |
48 |
LongVariable |
Avoid excessively long variable names like BYTES_PER_ENCODED_BLOCK |
49 |
LongVariable |
Avoid excessively long variable names like BYTES_PER_UNENCODED_BLOCK |
50 |
LongVariable |
Avoid excessively long variable names like UPPER_CASE_DECODE_TABLE |
57 |
LongVariable |
Avoid excessively long variable names like UPPER_CASE_ENCODE_TABLE |
71 |
LongVariable |
Avoid excessively long variable names like LOWER_CASE_DECODE_TABLE |
78 |
LongVariable |
Avoid excessively long variable names like LOWER_CASE_ENCODE_TABLE |
93 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the decode method if you want a default access modifier |
149–189 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
155 |
ConfusingTernary |
Avoid if (x != y) ..; else ..; |
158 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the encode method if you want a default access modifier |
203–224 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
205 |
org/apache/commons/codec/binary/Base32.java
Rule |
Violation |
Line |
LongVariable |
Avoid excessively long variable names like BITS_PER_ENCODED_BYTE |
84 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
84 |
LongVariable |
Avoid excessively long variable names like BYTES_PER_ENCODED_BLOCK |
86 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
86 |
LongVariable |
Avoid excessively long variable names like BYTES_PER_UNENCODED_BLOCK |
87 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
87 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
93–104 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
112–116 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
124–135 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
143–147 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
151 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
154 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
157 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
160 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
163 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
182 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
188 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
193 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
198 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the decode method if you want a default access modifier |
402–493 |
ShortVariable |
Avoid variables with short names like b |
412 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the encode method if you want a default access modifier |
507–600 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
510 |
PrematureDeclaration |
Avoid declaring a variable if it is unreferenced before a possible exit point. |
520 |
ShortVariable |
Avoid variables with short names like b |
577 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the getLineSeparator method if you want a default access modifier |
607–609 |
org/apache/commons/codec/binary/Base64.java
Rule |
Violation |
Line |
LinguisticNaming |
Linguistics Antipattern - The setter 'setUrlSafe' should not return any type except void linguistically |
97–99 |
LongVariable |
Avoid excessively long variable names like BITS_PER_ENCODED_BYTE |
108 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
108 |
LongVariable |
Avoid excessively long variable names like BYTES_PER_UNENCODED_BLOCK |
109 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
109 |
LongVariable |
Avoid excessively long variable names like BYTES_PER_ENCODED_BLOCK |
110 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
110 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
111 |
LongVariable |
Avoid excessively long variable names like DECODING_TABLE_LENGTH |
112 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
112 |
LongVariable |
Avoid excessively long variable names like STANDARD_ENCODE_TABLE |
122 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
122–128 |
LongVariable |
Avoid excessively long variable names like URL_SAFE_ENCODE_TABLE |
135 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
135–141 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
156–166 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
172 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
179 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
181 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
300 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
422 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the toIntegerBytes method if you want a default access modifier |
449–471 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
456 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
483 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
488 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
493 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
499 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
501 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the decode method if you want a default access modifier |
745–803 |
ShortVariable |
Avoid variables with short names like b |
755 |
ShortVariable |
Avoid variables with short names like in |
827 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the encode method if you want a default access modifier |
827–896 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
829 |
PrematureDeclaration |
Avoid declaring a variable if it is unreferenced before a possible exit point. |
839 |
ShortVariable |
Avoid variables with short names like b |
877 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the getLineSeparator method if you want a default access modifier |
903–905 |
org/apache/commons/codec/binary/BaseNCodec.java
Rule |
Violation |
Line |
LongVariable |
Avoid excessively long variable names like defaultEncodeTable |
67 |
LongVariable |
Avoid excessively long variable names like defaultEncodeTable |
72 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the AbstractBuilder constructor if you want a default access modifier |
72–75 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the asThis method if you want a default access modifier |
78–80 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the getDecodingPolicy method if you want a default access modifier |
82–84 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the getEncodeTable method if you want a default access modifier |
86–88 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the getLineLength method if you want a default access modifier |
90–92 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the getLineSeparator method if you want a default access modifier |
94–96 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the getPadding method if you want a default access modifier |
98–100 |
LinguisticNaming |
Linguistics Antipattern - The setter 'setDecodingPolicy' should not return any type except void linguistically |
108–111 |
LinguisticNaming |
Linguistics Antipattern - The setter 'setEncodeTable' should not return any type except void linguistically |
119–122 |
LinguisticNaming |
Linguistics Antipattern - The setter 'setLineLength' should not return any type except void linguistically |
130–133 |
LinguisticNaming |
Linguistics Antipattern - The setter 'setLineSeparator' should not return any type except void linguistically |
141–144 |
LinguisticNaming |
Linguistics Antipattern - The setter 'setPadding' should not return any type except void linguistically |
152–155 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the Context nested class if you want a default access modifier |
164–222 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the ibitWorkArea field if you want a default access modifier |
170 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the lbitWorkArea field if you want a default access modifier |
176 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the buffer field if you want a default access modifier |
181 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the pos field if you want a default access modifier |
186 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the readPos field if you want a default access modifier |
191 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the eof field if you want a default access modifier |
197 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the currentLinePos field if you want a default access modifier |
203 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the modulus field if you want a default access modifier |
209 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
229 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the EOF field if you want a default access modifier |
229 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
241 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
253 |
LongVariable |
Avoid excessively long variable names like DEFAULT_BUFFER_RESIZE_FACTOR |
255 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
255 |
LongVariable |
Avoid excessively long variable names like DEFAULT_BUFFER_SIZE |
261 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
261 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
273 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
276 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
281 |
LongVariable |
Avoid excessively long variable names like DECODING_POLICY_DEFAULT |
287 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
287 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
294 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the CHUNK_SEPARATOR field if you want a default access modifier |
294 |
ShortVariable |
Avoid variables with short names like b |
362 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the toLength method if you want a default access modifier |
373–375 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
381 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
384 |
LongVariable |
Avoid excessively long variable names like unencodedBlockSize |
387 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
387 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
390 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
397 |
LongVariable |
Avoid excessively long variable names like chunkSeparatorLength |
402 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
402 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
423 |
LongVariable |
Avoid excessively long variable names like chunkSeparatorLength |
437 |
LongVariable |
Avoid excessively long variable names like unencodedBlockSize |
437 |
LongVariable |
Avoid excessively long variable names like chunkSeparatorLength |
454 |
LongVariable |
Avoid excessively long variable names like unencodedBlockSize |
454 |
LongVariable |
Avoid excessively long variable names like chunkSeparatorLength |
473 |
LongVariable |
Avoid excessively long variable names like unencodedBlockSize |
473 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the available method if you want a default access modifier |
490–492 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
507 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
524 |
ShortVariable |
Avoid variables with short names like i |
535 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the decode method if you want a default access modifier |
535 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
551 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
580 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
600 |
ShortVariable |
Avoid variables with short names like i |
611 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the encode method if you want a default access modifier |
611 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
673 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the hasData method if you want a default access modifier |
728–730 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
755 |
ShortVariable |
Avoid variables with short names like b |
807 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the readResults method if you want a default access modifier |
807–822 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
819 |
org/apache/commons/codec/binary/BaseNCodecInputStream.java
Rule |
Violation |
Line |
ShortVariable |
Avoid variables with short names like r |
126 |
ShortVariable |
Avoid variables with short names like b |
131 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
132 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
166 |
ShortVariable |
Avoid variables with short names like c |
190 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
200 |
ConfusingTernary |
Avoid if (x != y) ..; else ..; |
200 |
ShortVariable |
Avoid variables with short names like n |
228 |
ShortVariable |
Avoid variables with short names like b |
233 |
org/apache/commons/codec/binary/BaseNCodecOutputStream.java
Rule |
Violation |
Line |
ShortVariable |
Avoid variables with short names like c |
122 |
ShortVariable |
Avoid variables with short names like i |
194 |
org/apache/commons/codec/binary/BinaryCodec.java
Rule |
Violation |
Line |
AtLeastOneConstructor |
Each class should declare at least one constructor |
35–299 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
81 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
109 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the isEmpty method if you want a default access modifier |
135–137 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
150 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
181 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
240 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
243 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
246 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
295 |
org/apache/commons/codec/binary/CharSequenceUtils.java
Rule |
Violation |
Line |
ShortVariable |
Avoid variables with short names like cs |
54 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the regionMatches method if you want a default access modifier |
54–78 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
57 |
ShortVariable |
Avoid variables with short names like c1 |
63 |
ShortVariable |
Avoid variables with short names like c2 |
64 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
69 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
74 |
org/apache/commons/codec/binary/Hex.java
Rule |
Violation |
Line |
LongVariable |
Avoid excessively long variable names like DEFAULT_CHARSET_NAME |
52 |
ShortVariable |
Avoid variables with short names like f |
102 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
348 |
ShortVariable |
Avoid variables with short names like ch |
365 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
373 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
452 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
455 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
458 |
org/apache/commons/codec/binary/StringUtils.java
Rule |
Violation |
Line |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
72 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
75 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
78 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
94 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
169 |
ShortVariable |
Avoid variables with short names like e |
269 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
310 |
UnnecessaryConstructor |
Avoid unnecessary constructors - the compiler will generate these for you |
421–423 |
org/apache/commons/codec/digest/Blake3.java
Rule |
Violation |
Line |
ShortVariable |
Avoid variables with short names like in |
166 |
LongVariable |
Avoid excessively long variable names like parentNodesRemaining |
191 |
ShortVariable |
Avoid variables with short names like cv |
203 |
LongVariable |
Avoid excessively long variable names like inputChainingValue |
220 |
LongVariable |
Avoid excessively long variable names like inputChainingValue |
226 |
LongVariable |
Avoid excessively long variable names like outputBlockCounter |
239 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
255 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
256 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
257 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
258 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
259 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
260 |
LongVariable |
Avoid excessively long variable names like CHAINING_VALUE_INTS |
261 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
261 |
ShortVariable |
Avoid variables with short names like IV |
266 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
266 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
269 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
270 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
271 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
272 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
273 |
LongVariable |
Avoid excessively long variable names like DERIVE_KEY_CONTEXT |
274 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
274 |
LongVariable |
Avoid excessively long variable names like DERIVE_KEY_MATERIAL |
275 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
275 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
281–289 |
ShortMethodName |
Avoid using short method names |
327–336 |
ShortVariable |
Avoid variables with short names like a |
327 |
ShortVariable |
Avoid variables with short names like b |
327 |
ShortVariable |
Avoid variables with short names like c |
327 |
ShortVariable |
Avoid variables with short names like d |
327 |
ShortVariable |
Avoid variables with short names like mx |
327 |
ShortVariable |
Avoid variables with short names like my |
327 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
447 |
ShortVariable |
Avoid variables with short names like in |
515 |
ShortVariable |
Avoid variables with short names like in |
530 |
org/apache/commons/codec/digest/Crypt.java
Rule |
Violation |
Line |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
75 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
78 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
81 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
84 |
UnnecessaryConstructor |
Avoid unnecessary constructors - the compiler will generate these for you |
180–182 |
org/apache/commons/codec/digest/DigestUtils.java
Rule |
Violation |
Line |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the BUFFER_SIZE field if you want a default access modifier |
63 |
LongVariable |
Avoid excessively long variable names like defaultMessageDigest |
174 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
176 |
LongVariable |
Avoid excessively long variable names like messageDigestAlgorithm |
353 |
UnnecessaryModifier |
Unnecessary modifier 'final' on resource specification 'inputStream': resource specifications are implicitly final |
1280 |
UnnecessaryModifier |
Unnecessary modifier 'final' on resource specification 'inputStream': resource specifications are implicitly final |
1338 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
1373 |
org/apache/commons/codec/digest/HmacUtils.java
Rule |
Violation |
Line |
LongVariable |
Avoid excessively long variable names like STREAM_BUFFER_LENGTH |
60 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
788 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
804 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
873 |
UnnecessaryModifier |
Unnecessary modifier 'final' on resource specification 'stream': resource specifications are implicitly final |
974 |
org/apache/commons/codec/digest/MurmurHash3.java
Rule |
Violation |
Line |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the finalise method if you want a default access modifier |
87–111 |
ShortVariable |
Avoid variables with short names like k1 |
92 |
ShortVariable |
Avoid variables with short names like b1 |
139 |
ShortVariable |
Avoid variables with short names like b2 |
139 |
ShortVariable |
Avoid variables with short names like b3 |
139 |
ShortVariable |
Avoid variables with short names like b4 |
139 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
144 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
147 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
150 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
156 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
168 |
ShortVariable |
Avoid variables with short names like k |
195 |
ShortVariable |
Avoid variables with short names like k |
224 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the finalise method if you want a default access modifier |
257–278 |
ShortVariable |
Avoid variables with short names like k1 |
259 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
298 |
UseUnderscoresInNumericLiterals |
Number 2862933555777941757L should separate every third digit with an underscore |
298 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
303 |
UseUnderscoresInNumericLiterals |
Number 104729 should separate every third digit with an underscore |
303 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
305 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
306 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
307 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
308 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
310 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
311 |
ShortVariable |
Avoid variables with short names like C1 |
313 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
313 |
ShortVariable |
Avoid variables with short names like C2 |
314 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
314 |
ShortVariable |
Avoid variables with short names like R1 |
315 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
315 |
ShortVariable |
Avoid variables with short names like R2 |
316 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
316 |
ShortVariable |
Avoid variables with short names like R3 |
317 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
317 |
ShortVariable |
Avoid variables with short names like M |
318 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
318 |
ShortVariable |
Avoid variables with short names like N1 |
320 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
320 |
ShortVariable |
Avoid variables with short names like N2 |
322 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
322 |
ShortVariable |
Avoid variables with short names like h1 |
516 |
ShortVariable |
Avoid variables with short names like h2 |
517 |
ShortVariable |
Avoid variables with short names like k1 |
523 |
ShortVariable |
Avoid variables with short names like k2 |
524 |
ShortVariable |
Avoid variables with short names like k1 |
546 |
ShortVariable |
Avoid variables with short names like k2 |
547 |
ShortVariable |
Avoid variables with short names like k |
706 |
ShortVariable |
Avoid variables with short names like k1 |
715 |
ShortVariable |
Avoid variables with short names like r0 |
773 |
ShortVariable |
Avoid variables with short names like r0 |
824 |
ShortVariable |
Avoid variables with short names like r1 |
825 |
ShortVariable |
Avoid variables with short names like k |
906 |
ShortVariable |
Avoid variables with short names like k1 |
912 |
ShortVariable |
Avoid variables with short names like k |
1036 |
ShortVariable |
Avoid variables with short names like k1 |
1047 |
ShortVariable |
Avoid variables with short names like k1 |
1106 |
ShortVariable |
Avoid variables with short names like k |
1149 |
ShortVariable |
Avoid variables with short names like k1 |
1193 |
ShortVariable |
Avoid variables with short names like k |
1213 |
org/apache/commons/codec/digest/XXHash32.java
Rule |
Violation |
Line |
UseUnderscoresInNumericLiterals |
Number 2654435761L should separate every third digit with an underscore |
43 |
UseUnderscoresInNumericLiterals |
Number 2246822519L should separate every third digit with an underscore |
44 |
UseUnderscoresInNumericLiterals |
Number 3266489917L should separate every third digit with an underscore |
45 |
UseUnderscoresInNumericLiterals |
Number 668265263 should separate every third digit with an underscore |
46 |
UseUnderscoresInNumericLiterals |
Number 374761393 should separate every third digit with an underscore |
47 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
62 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
63 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
66 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
68 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
69 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
71 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
74 |
ShortVariable |
Avoid variables with short names like b |
132 |
ShortVariable |
Avoid variables with short names like s0 |
134 |
ShortVariable |
Avoid variables with short names like s1 |
135 |
ShortVariable |
Avoid variables with short names like s2 |
136 |
ShortVariable |
Avoid variables with short names like s3 |
137 |
ShortVariable |
Avoid variables with short names like b |
161 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
163 |
PrematureDeclaration |
Avoid declaring a variable if it is unreferenced before a possible exit point. |
167 |
ShortVariable |
Avoid variables with short names like b |
202 |
org/apache/commons/codec/language/AbstractCaverphone.java
Rule |
Violation |
Line |
AtLeastOneConstructor |
Each class should declare at least one constructor |
34–72 |
org/apache/commons/codec/language/Caverphone.java
Rule |
Violation |
Line |
AtLeastOneConstructor |
Each class should declare at least one constructor |
35–97 |
org/apache/commons/codec/language/Caverphone1.java
Rule |
Violation |
Line |
AtLeastOneConstructor |
Each class should declare at least one constructor |
32–126 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
47 |
org/apache/commons/codec/language/Caverphone2.java
Rule |
Violation |
Line |
AtLeastOneConstructor |
Each class should declare at least one constructor |
32–130 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
47 |
org/apache/commons/codec/language/ColognePhonetic.java
Rule |
Violation |
Line |
AtLeastOneConstructor |
Each class should declare at least one constructor |
183–457 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the CologneBuffer nested class if you want a default access modifier |
190–220 |
ShortVariable |
Avoid variables with short names like ch |
243 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
279 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
280 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
281 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
282 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
283 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
284 |
ShortVariable |
Avoid variables with short names like SZ |
286 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
286 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
288 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
290 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
292 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
300 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
319 |
ConfusingTernary |
Avoid if (x != y) ..; else ..; |
333–337 |
org/apache/commons/codec/language/DaitchMokotoffSoundex.java
Rule |
Violation |
Line |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
101 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
104 |
LongVariable |
Avoid excessively long variable names like replacementAtStart |
162 |
LongVariable |
Avoid excessively long variable names like replacementBeforeVowel |
163 |
LongVariable |
Avoid excessively long variable names like replacementDefault |
164 |
LongVariable |
Avoid excessively long variable names like replacementAtStart |
166 |
LongVariable |
Avoid excessively long variable names like replacementBeforeVowel |
166 |
LongVariable |
Avoid excessively long variable names like replacementDefault |
167 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
180 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
186 |
ShortVariable |
Avoid variables with short names like ch |
192 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
207 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
209 |
LongVariable |
Avoid excessively long variable names like MULTILINE_COMMENT_END |
211 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
211 |
LongVariable |
Avoid excessively long variable names like MULTILINE_COMMENT_START |
213 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
213 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
216 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
219 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
222 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
225 |
UnnecessaryModifier |
Unnecessary modifier 'final' on resource specification 'scanner': resource specifications are implicitly final |
228 |
LongVariable |
Avoid excessively long variable names like inMultilineComment |
239 |
ShortVariable |
Avoid variables with short names like r |
298 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
324 |
ShortVariable |
Avoid variables with short names like sb |
358 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
415 |
ShortVariable |
Avoid variables with short names like sb |
445 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
468 |
ShortVariable |
Avoid variables with short names like ch |
478 |
org/apache/commons/codec/language/DoubleMetaphone.java
Rule |
Violation |
Line |
AtLeastOneConstructor |
Each class should declare at least one constructor |
37–993 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
119 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
123–124 |
LongVariable |
Avoid excessively long variable names like L_R_N_M_B_H_F_V_W_SPACE |
125 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
125–126 |
LongVariable |
Avoid excessively long variable names like ES_EP_EB_EL_EY_IB_IL_IN_IE_EI_ER |
127 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
127–128 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
130–131 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
156 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
165 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
175 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
179 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
189 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
192 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
195 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
198 |
ShortVariable |
Avoid variables with short names like c |
200 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
210 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
214 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
236 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
250 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
276 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
449 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
507 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
512 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
517 |
ConfusingTernary |
Avoid if (x != y) ..; else ..; |
565–570 |
ShortVariable |
Avoid variables with short names like ch |
980 |
org/apache/commons/codec/language/MatchRatingApproachEncoder.java
Rule |
Violation |
Line |
AtLeastOneConstructor |
Each class should declare at least one constructor |
33–425 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the cleanName method if you want a default access modifier |
78–88 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
121 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
129 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
138 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the getFirst3Last3 method if you want a default access modifier |
159–168 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
165 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the getMinRating method if you want a default access modifier |
183–199 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
214 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
217 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
220 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
223 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
247 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the isVowel method if you want a default access modifier |
277–280 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the leftToRightThenRightToLeftProcessing method if you want a default access modifier |
295–341 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
338 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the removeAccents method if you want a default access modifier |
351–370 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
353 |
ShortVariable |
Avoid variables with short names like sb |
356 |
ShortVariable |
Avoid variables with short names like n |
357 |
ShortVariable |
Avoid variables with short names like c |
360 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the removeDoubleConsonants method if you want a default access modifier |
384–393 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the removeVowels method if you want a default access modifier |
407–424 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
421 |
org/apache/commons/codec/language/Nysiis.java
Rule |
Violation |
Line |
ShortVariable |
Avoid variables with short names like c |
102 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
123 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
128 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
136 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
138 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
140 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
143 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
145 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
152 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
157 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
162 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
167 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
174 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
252 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
259 |
org/apache/commons/codec/language/RefinedSoundex.java
Rule |
Violation |
Line |
LongVariable |
Avoid excessively long variable names like US_ENGLISH_MAPPING_STRING |
49 |
LongVariable |
Avoid excessively long variable names like US_ENGLISH_MAPPING |
56 |
ShortVariable |
Avoid variables with short names like s1 |
126 |
ShortVariable |
Avoid variables with short names like s2 |
126 |
ShortVariable |
Avoid variables with short names like c |
172 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the getMappingCode method if you want a default access modifier |
172–181 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
174 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
178 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
192 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
196 |
org/apache/commons/codec/language/Soundex.java
Rule |
Violation |
Line |
LongVariable |
Avoid excessively long variable names like US_ENGLISH_MAPPING_STRING |
61 |
LongVariable |
Avoid excessively long variable names like US_ENGLISH_MAPPING |
69 |
LongVariable |
Avoid excessively long variable names like US_ENGLISH_SIMPLIFIED |
93 |
LongVariable |
Avoid excessively long variable names like US_ENGLISH_GENEALOGY |
110 |
ShortVariable |
Avoid variables with short names like s1 |
216 |
ShortVariable |
Avoid variables with short names like s2 |
216 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
269 |
ShortVariable |
Avoid variables with short names like ch |
284 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
315 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
319 |
ShortVariable |
Avoid variables with short names like ch |
327 |
org/apache/commons/codec/language/SoundexUtils.java
Rule |
Violation |
Line |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the clean method if you want a default access modifier |
40–56 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
42 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
53 |
ShortVariable |
Avoid variables with short names like s1 |
84 |
ShortVariable |
Avoid variables with short names like s2 |
84 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the difference method if you want a default access modifier |
84–86 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the differenceEncoded method if you want a default access modifier |
108–121 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
111 |
ShortVariable |
Avoid variables with short names like cs |
137 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the isEmpty method if you want a default access modifier |
137–139 |
org/apache/commons/codec/language/bm/BeiderMorseEncoder.java
Rule |
Violation |
Line |
AtLeastOneConstructor |
Each class should declare at least one constructor |
82–187 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
100 |
org/apache/commons/codec/language/bm/Lang.java
Rule |
Violation |
Line |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
102 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
104 |
LongVariable |
Avoid excessively long variable names like languageRulesResourceName |
136 |
UnnecessaryModifier |
Unnecessary modifier 'final' on resource specification 'scanner': resource specifications are implicitly final |
138–139 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
184 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
186 |
ShortVariable |
Avoid variables with short names like ls |
201 |
ShortVariable |
Avoid variables with short names like ls |
224 |
org/apache/commons/codec/language/bm/Languages.java
Rule |
Violation |
Line |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the merge method if you want a default access modifier |
85 |
CallSuperInConstructor |
It is a good practice to call super() in a constructor |
96–98 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
127 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
130 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
141 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
144 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
157 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
159 |
LongVariable |
Avoid excessively long variable names like languagesResourceName |
251 |
ShortVariable |
Avoid variables with short names like ls |
253 |
UnnecessaryModifier |
Unnecessary modifier 'final' on resource specification 'lsScanner': resource specifications are implicitly final |
254–255 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
277 |
org/apache/commons/codec/language/bm/PhoneticEngine.java
Rule |
Violation |
Line |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the PhonemeBuilder nested class if you want a default access modifier |
64–147 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
78 |
ShortVariable |
Avoid variables with short names like i |
168 |
ShortVariable |
Avoid variables with short names like i |
172 |
LongVariable |
Avoid excessively long variable names like DEFAULT_MAX_PHONEMES |
226 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
226 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
228 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
255 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
257 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
259 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
261 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
263 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
315 |
PrematureDeclaration |
Avoid declaring a variable if it is unreferenced before a possible exit point. |
377 |
PrematureDeclaration |
Avoid declaring a variable if it is unreferenced before a possible exit point. |
379 |
PrematureDeclaration |
Avoid declaring a variable if it is unreferenced before a possible exit point. |
381 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
391 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
399 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
438 |
org/apache/commons/codec/language/bm/ResourceConstants.java
Rule |
Violation |
Line |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the CMT field if you want a default access modifier |
31 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the ENCODING field if you want a default access modifier |
32 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the EXT_CMT_END field if you want a default access modifier |
33 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the EXT_CMT_START field if you want a default access modifier |
34 |
org/apache/commons/codec/language/bm/Rule.java
Rule |
Violation |
Line |
ShortVariable |
Avoid variables with short names like c |
96 |
LongVariable |
Avoid excessively long variable names like ALL_STRINGS_RMATCHER |
221 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
221 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
223 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
225 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
227 |
LongVariable |
Avoid excessively long variable names like HASH_INCLUDE_LENGTH |
229 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
229 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
231–232 |
ShortVariable |
Avoid variables with short names like rs |
240 |
ShortVariable |
Avoid variables with short names like ls |
242 |
UnnecessaryModifier |
Unnecessary modifier 'final' on resource specification 'scanner': resource specifications are implicitly final |
244 |
UnnecessaryModifier |
Unnecessary modifier 'final' on resource specification 'scanner': resource specifications are implicitly final |
251 |
ShortVariable |
Avoid variables with short names like rt |
267 |
ShortVariable |
Avoid variables with short names like rt |
273 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
289 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
293 |
ShortVariable |
Avoid variables with short names like rt |
310 |
ShortVariable |
Avoid variables with short names like rt |
329 |
ShortVariable |
Avoid variables with short names like rt |
345 |
ShortVariable |
Avoid variables with short names like rt |
363 |
ShortVariable |
Avoid variables with short names like ph |
375 |
ShortVariable |
Avoid variables with short names like in |
382 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
385 |
ShortVariable |
Avoid variables with short names like ph |
390 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
405 |
LongVariable |
Avoid excessively long variable names like inMultilineComment |
414 |
LongVariable |
Avoid excessively long variable names like hashIncludeScanner |
447 |
UnnecessaryModifier |
Unnecessary modifier 'final' on resource specification 'hashIncludeScanner': resource specifications are implicitly final |
447 |
ShortVariable |
Avoid variables with short names like ph |
461 |
ShortVariable |
Avoid variables with short names like r |
463 |
ShortVariable |
Avoid variables with short names like sb |
469 |
ConfusingTernary |
Avoid if (x != y) ..; else ..; |
507–558 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
512 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
514 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
518 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
522 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
526 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
545 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
549 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
553–554 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the pattern field if you want a default access modifier |
561 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
573 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
577 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
595 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
597 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
599 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
601 |
ShortVariable |
Avoid variables with short names like i |
669 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
679 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
685 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
688 |
org/apache/commons/codec/net/BCodec.java
Rule |
Violation |
Line |
LongVariable |
Avoid excessively long variable names like DECODING_POLICY_DEFAULT |
55 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
126 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
156 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
164 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
181 |
org/apache/commons/codec/net/PercentCodec.java
Rule |
Violation |
Line |
LongVariable |
Avoid excessively long variable names like alwaysEncodeCharsMax |
60 |
LongVariable |
Avoid excessively long variable names like alwaysEncodeCharsMin |
60 |
ShortVariable |
Avoid variables with short names like c |
85 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
92 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
105 |
ShortVariable |
Avoid variables with short names like b |
109 |
ShortVariable |
Avoid variables with short names like u |
112 |
ShortVariable |
Avoid variables with short names like l |
113 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
137 |
ShortVariable |
Avoid variables with short names like bb |
149 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
174 |
LongVariable |
Avoid excessively long variable names like expectedEncodingBytes |
176 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
179 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
194 |
ShortVariable |
Avoid variables with short names like b |
205 |
ShortVariable |
Avoid variables with short names like c |
220 |
ShortVariable |
Avoid variables with short names like b |
230 |
LongVariable |
Avoid excessively long variable names like alwaysEncodeCharsArray |
248 |
ShortVariable |
Avoid variables with short names like c |
257 |
org/apache/commons/codec/net/QCodec.java
Rule |
Violation |
Line |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
157 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
187 |
ShortVariable |
Avoid variables with short names like b |
199 |
ConfusingTernary |
Avoid if (x != y) ..; else ..; |
200–204 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
206 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
214 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
239 |
ShortVariable |
Avoid variables with short names like b |
316 |
org/apache/commons/codec/net/QuotedPrintableCodec.java
Rule |
Violation |
Line |
ShortVariable |
Avoid variables with short names like CR |
83 |
ShortVariable |
Avoid variables with short names like LF |
85 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
126 |
ShortVariable |
Avoid variables with short names like b |
130 |
ShortVariable |
Avoid variables with short names like u |
137 |
ShortVariable |
Avoid variables with short names like l |
138 |
ShortVariable |
Avoid variables with short names like b |
162 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
164 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
206 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
216 |
ShortVariable |
Avoid variables with short names like b |
223 |
ShortVariable |
Avoid variables with short names like b |
241 |
ShortVariable |
Avoid variables with short names like b |
261 |
ShortVariable |
Avoid variables with short names like b |
284 |
UnnecessaryModifier |
Unnecessary modifier 'final' on method 'encodeQuotedPrintable': private methods cannot be overridden |
284–291 |
ShortVariable |
Avoid variables with short names like b |
304 |
ShortVariable |
Avoid variables with short names like b |
318 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
325 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
330 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
427 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
430 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
469 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
490 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
525 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
528 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
574 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
597 |
org/apache/commons/codec/net/RFC1522Codec.java
Rule |
Violation |
Line |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the RFC1522Codec constructor if you want a default access modifier |
60–62 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
81 |
ShortVariable |
Avoid variables with short names like to |
88 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
152 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
186 |
org/apache/commons/codec/net/URLCodec.java
Rule |
Violation |
Line |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
104 |
ShortVariable |
Avoid variables with short names like b |
108 |
ShortVariable |
Avoid variables with short names like u |
113 |
ShortVariable |
Avoid variables with short names like l |
114 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
137 |
ShortVariable |
Avoid variables with short names like b |
145 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
171 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
218 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
221 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
243 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
269 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
298 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
301 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
323 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
345 |
Priority 4
org/apache/commons/codec/binary/Hex.java
Rule |
Violation |
Line |
ShortClassName |
Avoid short class names like Hex |
38–566 |
org/apache/commons/codec/digest/B64.java
Rule |
Violation |
Line |
ShortClassName |
Avoid short class names like B64 |
31–99 |
org/apache/commons/codec/language/DaitchMokotoffSoundex.java
Rule |
Violation |
Line |
ShortClassName |
Avoid short class names like Rule |
160–205 |
org/apache/commons/codec/language/bm/Lang.java
Rule |
Violation |
Line |
ShortClassName |
Avoid short class names like Lang |
77–227 |
org/apache/commons/codec/language/bm/Rule.java
Rule |
Violation |
Line |
ShortClassName |
Avoid short class names like Rule |
85–692 |
Files
org/apache/commons/codec/CharEncoding.java
Rule |
Violation |
Priority |
Line |
UnnecessaryConstructor |
Avoid unnecessary constructors - the compiler will generate these for you |
3 |
128–130 |
org/apache/commons/codec/Charsets.java
Rule |
Violation |
Priority |
Line |
UnnecessaryConstructor |
Avoid unnecessary constructors - the compiler will generate these for you |
3 |
169–171 |
org/apache/commons/codec/DecoderException.java
Rule |
Violation |
Priority |
Line |
CallSuperInConstructor |
It is a good practice to call super() in a constructor |
3 |
39–40 |
org/apache/commons/codec/EncoderException.java
Rule |
Violation |
Priority |
Line |
CallSuperInConstructor |
It is a good practice to call super() in a constructor |
3 |
40–41 |
org/apache/commons/codec/Resources.java
Rule |
Violation |
Priority |
Line |
UnnecessaryConstructor |
Avoid unnecessary constructors - the compiler will generate these for you |
3 |
49–51 |
org/apache/commons/codec/StringEncoderComparator.java
Rule |
Violation |
Priority |
Line |
ShortVariable |
Avoid variables with short names like o1 |
3 |
73 |
ShortVariable |
Avoid variables with short names like o2 |
3 |
73 |
ShortVariable |
Avoid variables with short names like s1 |
3 |
80 |
ShortVariable |
Avoid variables with short names like s2 |
3 |
81 |
org/apache/commons/codec/binary/Base16.java
Rule |
Violation |
Priority |
Line |
LongVariable |
Avoid excessively long variable names like BITS_PER_ENCODED_BYTE |
3 |
48 |
LongVariable |
Avoid excessively long variable names like BYTES_PER_ENCODED_BLOCK |
3 |
49 |
LongVariable |
Avoid excessively long variable names like BYTES_PER_UNENCODED_BLOCK |
3 |
50 |
LongVariable |
Avoid excessively long variable names like UPPER_CASE_DECODE_TABLE |
3 |
57 |
LongVariable |
Avoid excessively long variable names like UPPER_CASE_ENCODE_TABLE |
3 |
71 |
LongVariable |
Avoid excessively long variable names like LOWER_CASE_DECODE_TABLE |
3 |
78 |
LongVariable |
Avoid excessively long variable names like LOWER_CASE_ENCODE_TABLE |
3 |
93 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the decode method if you want a default access modifier |
3 |
149–189 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
155 |
ConfusingTernary |
Avoid if (x != y) ..; else ..; |
3 |
158 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the encode method if you want a default access modifier |
3 |
203–224 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
205 |
org/apache/commons/codec/binary/Base32.java
Rule |
Violation |
Priority |
Line |
LongVariable |
Avoid excessively long variable names like BITS_PER_ENCODED_BYTE |
3 |
84 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
84 |
LongVariable |
Avoid excessively long variable names like BYTES_PER_ENCODED_BLOCK |
3 |
86 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
86 |
LongVariable |
Avoid excessively long variable names like BYTES_PER_UNENCODED_BLOCK |
3 |
87 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
87 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
93–104 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
112–116 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
124–135 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
143–147 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
151 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
154 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
157 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
160 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
163 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
182 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
188 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
193 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
198 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the decode method if you want a default access modifier |
3 |
402–493 |
ShortVariable |
Avoid variables with short names like b |
3 |
412 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the encode method if you want a default access modifier |
3 |
507–600 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
510 |
PrematureDeclaration |
Avoid declaring a variable if it is unreferenced before a possible exit point. |
3 |
520 |
ShortVariable |
Avoid variables with short names like b |
3 |
577 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the getLineSeparator method if you want a default access modifier |
3 |
607–609 |
org/apache/commons/codec/binary/Base64.java
Rule |
Violation |
Priority |
Line |
LinguisticNaming |
Linguistics Antipattern - The setter 'setUrlSafe' should not return any type except void linguistically |
3 |
97–99 |
LongVariable |
Avoid excessively long variable names like BITS_PER_ENCODED_BYTE |
3 |
108 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
108 |
LongVariable |
Avoid excessively long variable names like BYTES_PER_UNENCODED_BLOCK |
3 |
109 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
109 |
LongVariable |
Avoid excessively long variable names like BYTES_PER_ENCODED_BLOCK |
3 |
110 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
110 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
111 |
LongVariable |
Avoid excessively long variable names like DECODING_TABLE_LENGTH |
3 |
112 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
112 |
LongVariable |
Avoid excessively long variable names like STANDARD_ENCODE_TABLE |
3 |
122 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
122–128 |
LongVariable |
Avoid excessively long variable names like URL_SAFE_ENCODE_TABLE |
3 |
135 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
135–141 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
156–166 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
172 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
179 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
181 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
300 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
422 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the toIntegerBytes method if you want a default access modifier |
3 |
449–471 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
456 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
483 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
488 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
493 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
499 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
501 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the decode method if you want a default access modifier |
3 |
745–803 |
ShortVariable |
Avoid variables with short names like b |
3 |
755 |
ShortVariable |
Avoid variables with short names like in |
3 |
827 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the encode method if you want a default access modifier |
3 |
827–896 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
829 |
PrematureDeclaration |
Avoid declaring a variable if it is unreferenced before a possible exit point. |
3 |
839 |
ShortVariable |
Avoid variables with short names like b |
3 |
877 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the getLineSeparator method if you want a default access modifier |
3 |
903–905 |
org/apache/commons/codec/binary/BaseNCodec.java
Rule |
Violation |
Priority |
Line |
LongVariable |
Avoid excessively long variable names like defaultEncodeTable |
3 |
67 |
LongVariable |
Avoid excessively long variable names like defaultEncodeTable |
3 |
72 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the AbstractBuilder constructor if you want a default access modifier |
3 |
72–75 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the asThis method if you want a default access modifier |
3 |
78–80 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the getDecodingPolicy method if you want a default access modifier |
3 |
82–84 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the getEncodeTable method if you want a default access modifier |
3 |
86–88 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the getLineLength method if you want a default access modifier |
3 |
90–92 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the getLineSeparator method if you want a default access modifier |
3 |
94–96 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the getPadding method if you want a default access modifier |
3 |
98–100 |
LinguisticNaming |
Linguistics Antipattern - The setter 'setDecodingPolicy' should not return any type except void linguistically |
3 |
108–111 |
LinguisticNaming |
Linguistics Antipattern - The setter 'setEncodeTable' should not return any type except void linguistically |
3 |
119–122 |
LinguisticNaming |
Linguistics Antipattern - The setter 'setLineLength' should not return any type except void linguistically |
3 |
130–133 |
LinguisticNaming |
Linguistics Antipattern - The setter 'setLineSeparator' should not return any type except void linguistically |
3 |
141–144 |
LinguisticNaming |
Linguistics Antipattern - The setter 'setPadding' should not return any type except void linguistically |
3 |
152–155 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the Context nested class if you want a default access modifier |
3 |
164–222 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the ibitWorkArea field if you want a default access modifier |
3 |
170 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the lbitWorkArea field if you want a default access modifier |
3 |
176 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the buffer field if you want a default access modifier |
3 |
181 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the pos field if you want a default access modifier |
3 |
186 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the readPos field if you want a default access modifier |
3 |
191 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the eof field if you want a default access modifier |
3 |
197 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the currentLinePos field if you want a default access modifier |
3 |
203 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the modulus field if you want a default access modifier |
3 |
209 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
229 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the EOF field if you want a default access modifier |
3 |
229 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
241 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
253 |
LongVariable |
Avoid excessively long variable names like DEFAULT_BUFFER_RESIZE_FACTOR |
3 |
255 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
255 |
LongVariable |
Avoid excessively long variable names like DEFAULT_BUFFER_SIZE |
3 |
261 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
261 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
273 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
276 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
281 |
LongVariable |
Avoid excessively long variable names like DECODING_POLICY_DEFAULT |
3 |
287 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
287 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
294 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the CHUNK_SEPARATOR field if you want a default access modifier |
3 |
294 |
ShortVariable |
Avoid variables with short names like b |
3 |
362 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the toLength method if you want a default access modifier |
3 |
373–375 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
381 |
FieldNamingConventions |
The final field name 'PAD' doesn't match '[a-z][a-zA-Z0-9]*' |
1 |
381 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
384 |
LongVariable |
Avoid excessively long variable names like unencodedBlockSize |
3 |
387 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
387 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
390 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
397 |
LongVariable |
Avoid excessively long variable names like chunkSeparatorLength |
3 |
402 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
402 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
423 |
LongVariable |
Avoid excessively long variable names like chunkSeparatorLength |
3 |
437 |
LongVariable |
Avoid excessively long variable names like unencodedBlockSize |
3 |
437 |
LongVariable |
Avoid excessively long variable names like chunkSeparatorLength |
3 |
454 |
LongVariable |
Avoid excessively long variable names like unencodedBlockSize |
3 |
454 |
LongVariable |
Avoid excessively long variable names like chunkSeparatorLength |
3 |
473 |
LongVariable |
Avoid excessively long variable names like unencodedBlockSize |
3 |
473 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the available method if you want a default access modifier |
3 |
490–492 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
507 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
524 |
ShortVariable |
Avoid variables with short names like i |
3 |
535 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the decode method if you want a default access modifier |
3 |
535 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
551 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
580 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
600 |
ShortVariable |
Avoid variables with short names like i |
3 |
611 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the encode method if you want a default access modifier |
3 |
611 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
673 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the hasData method if you want a default access modifier |
3 |
728–730 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
755 |
ShortVariable |
Avoid variables with short names like b |
3 |
807 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the readResults method if you want a default access modifier |
3 |
807–822 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
819 |
org/apache/commons/codec/binary/BaseNCodecInputStream.java
Rule |
Violation |
Priority |
Line |
ShortVariable |
Avoid variables with short names like r |
3 |
126 |
ShortVariable |
Avoid variables with short names like b |
3 |
131 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
132 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
166 |
ShortVariable |
Avoid variables with short names like c |
3 |
190 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
200 |
ConfusingTernary |
Avoid if (x != y) ..; else ..; |
3 |
200 |
ShortVariable |
Avoid variables with short names like n |
3 |
228 |
ShortVariable |
Avoid variables with short names like b |
3 |
233 |
org/apache/commons/codec/binary/BaseNCodecOutputStream.java
Rule |
Violation |
Priority |
Line |
ShortVariable |
Avoid variables with short names like c |
3 |
122 |
ShortVariable |
Avoid variables with short names like i |
3 |
194 |
org/apache/commons/codec/binary/BinaryCodec.java
Rule |
Violation |
Priority |
Line |
AtLeastOneConstructor |
Each class should declare at least one constructor |
3 |
35–299 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
81 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
109 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the isEmpty method if you want a default access modifier |
3 |
135–137 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
150 |
LocalVariableNamingConventions |
The final local variable name 'l_ascii' doesn't match '[a-z][a-zA-Z0-9]*' |
1 |
154 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
181 |
LocalVariableNamingConventions |
The final local variable name 'l_ascii' doesn't match '[a-z][a-zA-Z0-9]*' |
1 |
185 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
240 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
243 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
246 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
295 |
org/apache/commons/codec/binary/CharSequenceUtils.java
Rule |
Violation |
Priority |
Line |
ShortVariable |
Avoid variables with short names like cs |
3 |
54 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the regionMatches method if you want a default access modifier |
3 |
54–78 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
57 |
ShortVariable |
Avoid variables with short names like c1 |
3 |
63 |
ShortVariable |
Avoid variables with short names like c2 |
3 |
64 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
69 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
74 |
org/apache/commons/codec/binary/Hex.java
Rule |
Violation |
Priority |
Line |
ShortClassName |
Avoid short class names like Hex |
4 |
38–566 |
LongVariable |
Avoid excessively long variable names like DEFAULT_CHARSET_NAME |
3 |
52 |
ShortVariable |
Avoid variables with short names like f |
3 |
102 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
348 |
ShortVariable |
Avoid variables with short names like ch |
3 |
365 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
373 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
452 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
455 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
458 |
org/apache/commons/codec/binary/StringUtils.java
Rule |
Violation |
Priority |
Line |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
72 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
75 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
78 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
94 |
MethodNamingConventions |
The static method name 'getBytesIso8859_1' doesn't match '[a-z][a-zA-Z0-9]*' |
1 |
144–146 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
169 |
ShortVariable |
Avoid variables with short names like e |
3 |
269 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
310 |
MethodNamingConventions |
The static method name 'newStringIso8859_1' doesn't match '[a-z][a-zA-Z0-9]*' |
1 |
331–333 |
UnnecessaryConstructor |
Avoid unnecessary constructors - the compiler will generate these for you |
3 |
421–423 |
org/apache/commons/codec/digest/Blake3.java
Rule |
Violation |
Priority |
Line |
ShortVariable |
Avoid variables with short names like in |
3 |
166 |
LongVariable |
Avoid excessively long variable names like parentNodesRemaining |
3 |
191 |
ShortVariable |
Avoid variables with short names like cv |
3 |
203 |
LongVariable |
Avoid excessively long variable names like inputChainingValue |
3 |
220 |
LongVariable |
Avoid excessively long variable names like inputChainingValue |
3 |
226 |
LongVariable |
Avoid excessively long variable names like outputBlockCounter |
3 |
239 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
255 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
256 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
257 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
258 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
259 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
260 |
LongVariable |
Avoid excessively long variable names like CHAINING_VALUE_INTS |
3 |
261 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
261 |
ShortVariable |
Avoid variables with short names like IV |
3 |
266 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
266 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
269 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
270 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
271 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
272 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
273 |
LongVariable |
Avoid excessively long variable names like DERIVE_KEY_CONTEXT |
3 |
274 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
274 |
LongVariable |
Avoid excessively long variable names like DERIVE_KEY_MATERIAL |
3 |
275 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
275 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
281–289 |
ShortMethodName |
Avoid using short method names |
3 |
327–336 |
ShortVariable |
Avoid variables with short names like a |
3 |
327 |
ShortVariable |
Avoid variables with short names like b |
3 |
327 |
ShortVariable |
Avoid variables with short names like c |
3 |
327 |
ShortVariable |
Avoid variables with short names like d |
3 |
327 |
ShortVariable |
Avoid variables with short names like mx |
3 |
327 |
ShortVariable |
Avoid variables with short names like my |
3 |
327 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
447 |
ShortVariable |
Avoid variables with short names like in |
3 |
515 |
ShortVariable |
Avoid variables with short names like in |
3 |
530 |
org/apache/commons/codec/digest/Crypt.java
Rule |
Violation |
Priority |
Line |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
75 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
78 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
81 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
84 |
UnnecessaryConstructor |
Avoid unnecessary constructors - the compiler will generate these for you |
3 |
180–182 |
org/apache/commons/codec/digest/HmacUtils.java
Rule |
Violation |
Priority |
Line |
LongVariable |
Avoid excessively long variable names like STREAM_BUFFER_LENGTH |
3 |
60 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
788 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
804 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
873 |
UnnecessaryModifier |
Unnecessary modifier 'final' on resource specification 'stream': resource specifications are implicitly final |
3 |
974 |
org/apache/commons/codec/digest/MurmurHash3.java
Rule |
Violation |
Priority |
Line |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the finalise method if you want a default access modifier |
3 |
87–111 |
ShortVariable |
Avoid variables with short names like k1 |
3 |
92 |
ShortVariable |
Avoid variables with short names like b1 |
3 |
139 |
ShortVariable |
Avoid variables with short names like b2 |
3 |
139 |
ShortVariable |
Avoid variables with short names like b3 |
3 |
139 |
ShortVariable |
Avoid variables with short names like b4 |
3 |
139 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
144 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
147 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
150 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
156 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
168 |
ShortVariable |
Avoid variables with short names like k |
3 |
195 |
ShortVariable |
Avoid variables with short names like k |
3 |
224 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the finalise method if you want a default access modifier |
3 |
257–278 |
ShortVariable |
Avoid variables with short names like k1 |
3 |
259 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
298 |
UseUnderscoresInNumericLiterals |
Number 2862933555777941757L should separate every third digit with an underscore |
3 |
298 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
303 |
UseUnderscoresInNumericLiterals |
Number 104729 should separate every third digit with an underscore |
3 |
303 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
305 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
306 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
307 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
308 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
310 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
311 |
ShortVariable |
Avoid variables with short names like C1 |
3 |
313 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
313 |
ShortVariable |
Avoid variables with short names like C2 |
3 |
314 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
314 |
ShortVariable |
Avoid variables with short names like R1 |
3 |
315 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
315 |
ShortVariable |
Avoid variables with short names like R2 |
3 |
316 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
316 |
ShortVariable |
Avoid variables with short names like R3 |
3 |
317 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
317 |
ShortVariable |
Avoid variables with short names like M |
3 |
318 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
318 |
ShortVariable |
Avoid variables with short names like N1 |
3 |
320 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
320 |
ShortVariable |
Avoid variables with short names like N2 |
3 |
322 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
322 |
ShortVariable |
Avoid variables with short names like h1 |
3 |
516 |
ShortVariable |
Avoid variables with short names like h2 |
3 |
517 |
ShortVariable |
Avoid variables with short names like k1 |
3 |
523 |
ShortVariable |
Avoid variables with short names like k2 |
3 |
524 |
ShortVariable |
Avoid variables with short names like k1 |
3 |
546 |
ShortVariable |
Avoid variables with short names like k2 |
3 |
547 |
ShortVariable |
Avoid variables with short names like k |
3 |
706 |
ShortVariable |
Avoid variables with short names like k1 |
3 |
715 |
ShortVariable |
Avoid variables with short names like r0 |
3 |
773 |
ShortVariable |
Avoid variables with short names like r0 |
3 |
824 |
ShortVariable |
Avoid variables with short names like r1 |
3 |
825 |
ShortVariable |
Avoid variables with short names like k |
3 |
906 |
ShortVariable |
Avoid variables with short names like k1 |
3 |
912 |
ShortVariable |
Avoid variables with short names like k |
3 |
1036 |
ShortVariable |
Avoid variables with short names like k1 |
3 |
1047 |
ShortVariable |
Avoid variables with short names like k1 |
3 |
1106 |
ShortVariable |
Avoid variables with short names like k |
3 |
1149 |
ShortVariable |
Avoid variables with short names like k1 |
3 |
1193 |
ShortVariable |
Avoid variables with short names like k |
3 |
1213 |
org/apache/commons/codec/digest/XXHash32.java
Rule |
Violation |
Priority |
Line |
UseUnderscoresInNumericLiterals |
Number 2654435761L should separate every third digit with an underscore |
3 |
43 |
UseUnderscoresInNumericLiterals |
Number 2246822519L should separate every third digit with an underscore |
3 |
44 |
UseUnderscoresInNumericLiterals |
Number 3266489917L should separate every third digit with an underscore |
3 |
45 |
UseUnderscoresInNumericLiterals |
Number 668265263 should separate every third digit with an underscore |
3 |
46 |
UseUnderscoresInNumericLiterals |
Number 374761393 should separate every third digit with an underscore |
3 |
47 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
62 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
63 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
66 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
68 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
69 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
71 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
74 |
ShortVariable |
Avoid variables with short names like b |
3 |
132 |
ShortVariable |
Avoid variables with short names like s0 |
3 |
134 |
ShortVariable |
Avoid variables with short names like s1 |
3 |
135 |
ShortVariable |
Avoid variables with short names like s2 |
3 |
136 |
ShortVariable |
Avoid variables with short names like s3 |
3 |
137 |
ShortVariable |
Avoid variables with short names like b |
3 |
161 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
163 |
PrematureDeclaration |
Avoid declaring a variable if it is unreferenced before a possible exit point. |
3 |
167 |
ShortVariable |
Avoid variables with short names like b |
3 |
202 |
org/apache/commons/codec/language/AbstractCaverphone.java
Rule |
Violation |
Priority |
Line |
AtLeastOneConstructor |
Each class should declare at least one constructor |
3 |
34–72 |
org/apache/commons/codec/language/Caverphone.java
Rule |
Violation |
Priority |
Line |
AtLeastOneConstructor |
Each class should declare at least one constructor |
3 |
35–97 |
org/apache/commons/codec/language/Caverphone1.java
Rule |
Violation |
Priority |
Line |
AtLeastOneConstructor |
Each class should declare at least one constructor |
3 |
32–126 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
47 |
org/apache/commons/codec/language/Caverphone2.java
Rule |
Violation |
Priority |
Line |
AtLeastOneConstructor |
Each class should declare at least one constructor |
3 |
32–130 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
47 |
org/apache/commons/codec/language/ColognePhonetic.java
Rule |
Violation |
Priority |
Line |
AtLeastOneConstructor |
Each class should declare at least one constructor |
3 |
183–457 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the CologneBuffer nested class if you want a default access modifier |
3 |
190–220 |
ShortVariable |
Avoid variables with short names like ch |
3 |
243 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
279 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
280 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
281 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
282 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
283 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
284 |
ShortVariable |
Avoid variables with short names like SZ |
3 |
286 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
286 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
288 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
290 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
292 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
300 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
319 |
ConfusingTernary |
Avoid if (x != y) ..; else ..; |
3 |
333–337 |
org/apache/commons/codec/language/DaitchMokotoffSoundex.java
Rule |
Violation |
Priority |
Line |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
101 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
104 |
ShortClassName |
Avoid short class names like Rule |
4 |
160–205 |
LongVariable |
Avoid excessively long variable names like replacementAtStart |
3 |
162 |
LongVariable |
Avoid excessively long variable names like replacementBeforeVowel |
3 |
163 |
LongVariable |
Avoid excessively long variable names like replacementDefault |
3 |
164 |
LongVariable |
Avoid excessively long variable names like replacementAtStart |
3 |
166 |
LongVariable |
Avoid excessively long variable names like replacementBeforeVowel |
3 |
166 |
LongVariable |
Avoid excessively long variable names like replacementDefault |
3 |
167 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
180 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
186 |
ShortVariable |
Avoid variables with short names like ch |
3 |
192 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
207 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
209 |
LongVariable |
Avoid excessively long variable names like MULTILINE_COMMENT_END |
3 |
211 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
211 |
LongVariable |
Avoid excessively long variable names like MULTILINE_COMMENT_START |
3 |
213 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
213 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
216 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
219 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
222 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
225 |
UnnecessaryModifier |
Unnecessary modifier 'final' on resource specification 'scanner': resource specifications are implicitly final |
3 |
228 |
LongVariable |
Avoid excessively long variable names like inMultilineComment |
3 |
239 |
ShortVariable |
Avoid variables with short names like r |
3 |
298 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
324 |
ShortVariable |
Avoid variables with short names like sb |
3 |
358 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
415 |
ShortVariable |
Avoid variables with short names like sb |
3 |
445 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
468 |
ShortVariable |
Avoid variables with short names like ch |
3 |
478 |
org/apache/commons/codec/language/DoubleMetaphone.java
Rule |
Violation |
Priority |
Line |
AtLeastOneConstructor |
Each class should declare at least one constructor |
3 |
37–993 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
119 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
123–124 |
LongVariable |
Avoid excessively long variable names like L_R_N_M_B_H_F_V_W_SPACE |
3 |
125 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
125–126 |
LongVariable |
Avoid excessively long variable names like ES_EP_EB_EL_EY_IB_IL_IN_IE_EI_ER |
3 |
127 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
127–128 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
130–131 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
156 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
165 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
175 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
179 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
189 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
192 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
195 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
198 |
ShortVariable |
Avoid variables with short names like c |
3 |
200 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
210 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
214 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
236 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
250 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
276 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
449 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
507 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
512 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
517 |
ConfusingTernary |
Avoid if (x != y) ..; else ..; |
3 |
565–570 |
ShortVariable |
Avoid variables with short names like ch |
3 |
980 |
org/apache/commons/codec/language/MatchRatingApproachEncoder.java
Rule |
Violation |
Priority |
Line |
AtLeastOneConstructor |
Each class should declare at least one constructor |
3 |
33–425 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the cleanName method if you want a default access modifier |
3 |
78–88 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
121 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
129 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
138 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the getFirst3Last3 method if you want a default access modifier |
3 |
159–168 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
165 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the getMinRating method if you want a default access modifier |
3 |
183–199 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
214 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
217 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
220 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
223 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
247 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the isVowel method if you want a default access modifier |
3 |
277–280 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the leftToRightThenRightToLeftProcessing method if you want a default access modifier |
3 |
295–341 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
338 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the removeAccents method if you want a default access modifier |
3 |
351–370 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
353 |
ShortVariable |
Avoid variables with short names like sb |
3 |
356 |
ShortVariable |
Avoid variables with short names like n |
3 |
357 |
ShortVariable |
Avoid variables with short names like c |
3 |
360 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the removeDoubleConsonants method if you want a default access modifier |
3 |
384–393 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the removeVowels method if you want a default access modifier |
3 |
407–424 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
421 |
org/apache/commons/codec/language/Metaphone.java
Rule |
Violation |
Priority |
Line |
AtLeastOneConstructor |
Each class should declare at least one constructor |
3 |
55–397 |
ShortVariable |
Avoid variables with short names like n |
3 |
114 |
ShortVariable |
Avoid variables with short names like c |
3 |
130 |
ShortVariable |
Avoid variables with short names like c |
3 |
138 |
PrematureDeclaration |
Avoid declaring a variable if it is unreferenced before a possible exit point. |
3 |
161 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
164 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
168 |
ShortVariable |
Avoid variables with short names like n |
3 |
214 |
org/apache/commons/codec/language/Nysiis.java
Rule |
Violation |
Priority |
Line |
ShortVariable |
Avoid variables with short names like c |
3 |
102 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
123 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
128 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
136 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
138 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
140 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
143 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
145 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
152 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
157 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
162 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
167 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
174 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
252 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
259 |
org/apache/commons/codec/language/RefinedSoundex.java
Rule |
Violation |
Priority |
Line |
LongVariable |
Avoid excessively long variable names like US_ENGLISH_MAPPING_STRING |
3 |
49 |
LongVariable |
Avoid excessively long variable names like US_ENGLISH_MAPPING |
3 |
56 |
ShortVariable |
Avoid variables with short names like s1 |
3 |
126 |
ShortVariable |
Avoid variables with short names like s2 |
3 |
126 |
ShortVariable |
Avoid variables with short names like c |
3 |
172 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the getMappingCode method if you want a default access modifier |
3 |
172–181 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
174 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
178 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
192 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
196 |
org/apache/commons/codec/language/Soundex.java
Rule |
Violation |
Priority |
Line |
LongVariable |
Avoid excessively long variable names like US_ENGLISH_MAPPING_STRING |
3 |
61 |
LongVariable |
Avoid excessively long variable names like US_ENGLISH_MAPPING |
3 |
69 |
LongVariable |
Avoid excessively long variable names like US_ENGLISH_SIMPLIFIED |
3 |
93 |
LongVariable |
Avoid excessively long variable names like US_ENGLISH_GENEALOGY |
3 |
110 |
ShortVariable |
Avoid variables with short names like s1 |
3 |
216 |
ShortVariable |
Avoid variables with short names like s2 |
3 |
216 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
269 |
ShortVariable |
Avoid variables with short names like ch |
3 |
284 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
315 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
319 |
ShortVariable |
Avoid variables with short names like ch |
3 |
327 |
org/apache/commons/codec/language/SoundexUtils.java
Rule |
Violation |
Priority |
Line |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the clean method if you want a default access modifier |
3 |
40–56 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
42 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
53 |
ShortVariable |
Avoid variables with short names like s1 |
3 |
84 |
ShortVariable |
Avoid variables with short names like s2 |
3 |
84 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the difference method if you want a default access modifier |
3 |
84–86 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the differenceEncoded method if you want a default access modifier |
3 |
108–121 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
111 |
ShortVariable |
Avoid variables with short names like cs |
3 |
137 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the isEmpty method if you want a default access modifier |
3 |
137–139 |
org/apache/commons/codec/language/bm/BeiderMorseEncoder.java
Rule |
Violation |
Priority |
Line |
AtLeastOneConstructor |
Each class should declare at least one constructor |
3 |
82–187 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
100 |
org/apache/commons/codec/language/bm/Lang.java
Rule |
Violation |
Priority |
Line |
ShortClassName |
Avoid short class names like Lang |
4 |
77–227 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
102 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
104 |
LongVariable |
Avoid excessively long variable names like languageRulesResourceName |
3 |
136 |
UnnecessaryModifier |
Unnecessary modifier 'final' on resource specification 'scanner': resource specifications are implicitly final |
3 |
138–139 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
184 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
186 |
ShortVariable |
Avoid variables with short names like ls |
3 |
201 |
ShortVariable |
Avoid variables with short names like ls |
3 |
224 |
org/apache/commons/codec/language/bm/Languages.java
Rule |
Violation |
Priority |
Line |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the merge method if you want a default access modifier |
3 |
85 |
CallSuperInConstructor |
It is a good practice to call super() in a constructor |
3 |
96–98 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
127 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
130 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
141 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
144 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
157 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
159 |
LongVariable |
Avoid excessively long variable names like languagesResourceName |
3 |
251 |
ShortVariable |
Avoid variables with short names like ls |
3 |
253 |
UnnecessaryModifier |
Unnecessary modifier 'final' on resource specification 'lsScanner': resource specifications are implicitly final |
3 |
254–255 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
277 |
org/apache/commons/codec/language/bm/PhoneticEngine.java
Rule |
Violation |
Priority |
Line |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the PhonemeBuilder nested class if you want a default access modifier |
3 |
64–147 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
78 |
ShortVariable |
Avoid variables with short names like i |
3 |
168 |
ShortVariable |
Avoid variables with short names like i |
3 |
172 |
LongVariable |
Avoid excessively long variable names like DEFAULT_MAX_PHONEMES |
3 |
226 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
226 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
228 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
255 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
257 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
259 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
261 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
263 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
315 |
PrematureDeclaration |
Avoid declaring a variable if it is unreferenced before a possible exit point. |
3 |
377 |
PrematureDeclaration |
Avoid declaring a variable if it is unreferenced before a possible exit point. |
3 |
379 |
PrematureDeclaration |
Avoid declaring a variable if it is unreferenced before a possible exit point. |
3 |
381 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
391 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
399 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
438 |
org/apache/commons/codec/language/bm/ResourceConstants.java
Rule |
Violation |
Priority |
Line |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the CMT field if you want a default access modifier |
3 |
31 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the ENCODING field if you want a default access modifier |
3 |
32 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the EXT_CMT_END field if you want a default access modifier |
3 |
33 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the EXT_CMT_START field if you want a default access modifier |
3 |
34 |
org/apache/commons/codec/language/bm/Rule.java
Rule |
Violation |
Priority |
Line |
ShortClassName |
Avoid short class names like Rule |
4 |
85–692 |
ShortVariable |
Avoid variables with short names like c |
3 |
96 |
LongVariable |
Avoid excessively long variable names like ALL_STRINGS_RMATCHER |
3 |
221 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
221 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
223 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
225 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
227 |
LongVariable |
Avoid excessively long variable names like HASH_INCLUDE_LENGTH |
3 |
229 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
229 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
231–232 |
ShortVariable |
Avoid variables with short names like rs |
3 |
240 |
ShortVariable |
Avoid variables with short names like ls |
3 |
242 |
UnnecessaryModifier |
Unnecessary modifier 'final' on resource specification 'scanner': resource specifications are implicitly final |
3 |
244 |
UnnecessaryModifier |
Unnecessary modifier 'final' on resource specification 'scanner': resource specifications are implicitly final |
3 |
251 |
ShortVariable |
Avoid variables with short names like rt |
3 |
267 |
ShortVariable |
Avoid variables with short names like rt |
3 |
273 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
289 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
293 |
ShortVariable |
Avoid variables with short names like rt |
3 |
310 |
ShortVariable |
Avoid variables with short names like rt |
3 |
329 |
ShortVariable |
Avoid variables with short names like rt |
3 |
345 |
ShortVariable |
Avoid variables with short names like rt |
3 |
363 |
ShortVariable |
Avoid variables with short names like ph |
3 |
375 |
ShortVariable |
Avoid variables with short names like in |
3 |
382 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
385 |
ShortVariable |
Avoid variables with short names like ph |
3 |
390 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
405 |
LongVariable |
Avoid excessively long variable names like inMultilineComment |
3 |
414 |
LongVariable |
Avoid excessively long variable names like hashIncludeScanner |
3 |
447 |
UnnecessaryModifier |
Unnecessary modifier 'final' on resource specification 'hashIncludeScanner': resource specifications are implicitly final |
3 |
447 |
ShortVariable |
Avoid variables with short names like ph |
3 |
461 |
ShortVariable |
Avoid variables with short names like r |
3 |
463 |
ShortVariable |
Avoid variables with short names like sb |
3 |
469 |
ConfusingTernary |
Avoid if (x != y) ..; else ..; |
3 |
507–558 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
512 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
514 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
518 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
522 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
526 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
545 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
549 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
553–554 |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the pattern field if you want a default access modifier |
3 |
561 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
573 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
577 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
595 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
597 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
599 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
601 |
ShortVariable |
Avoid variables with short names like i |
3 |
669 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
679 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
685 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
688 |
org/apache/commons/codec/net/BCodec.java
Rule |
Violation |
Priority |
Line |
LongVariable |
Avoid excessively long variable names like DECODING_POLICY_DEFAULT |
3 |
55 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
126 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
156 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
164 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
181 |
org/apache/commons/codec/net/PercentCodec.java
Rule |
Violation |
Priority |
Line |
LongVariable |
Avoid excessively long variable names like alwaysEncodeCharsMax |
3 |
60 |
LongVariable |
Avoid excessively long variable names like alwaysEncodeCharsMin |
3 |
60 |
ShortVariable |
Avoid variables with short names like c |
3 |
85 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
92 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
105 |
ShortVariable |
Avoid variables with short names like b |
3 |
109 |
ShortVariable |
Avoid variables with short names like u |
3 |
112 |
ShortVariable |
Avoid variables with short names like l |
3 |
113 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
137 |
ShortVariable |
Avoid variables with short names like bb |
3 |
149 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
174 |
LongVariable |
Avoid excessively long variable names like expectedEncodingBytes |
3 |
176 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
179 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
194 |
ShortVariable |
Avoid variables with short names like b |
3 |
205 |
ShortVariable |
Avoid variables with short names like c |
3 |
220 |
ShortVariable |
Avoid variables with short names like b |
3 |
230 |
LongVariable |
Avoid excessively long variable names like alwaysEncodeCharsArray |
3 |
248 |
ShortVariable |
Avoid variables with short names like c |
3 |
257 |
org/apache/commons/codec/net/QCodec.java
Rule |
Violation |
Priority |
Line |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
157 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
187 |
ShortVariable |
Avoid variables with short names like b |
3 |
199 |
ConfusingTernary |
Avoid if (x != y) ..; else ..; |
3 |
200–204 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
206 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
214 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
239 |
ShortVariable |
Avoid variables with short names like b |
3 |
316 |
org/apache/commons/codec/net/QuotedPrintableCodec.java
Rule |
Violation |
Priority |
Line |
ShortVariable |
Avoid variables with short names like CR |
3 |
83 |
ShortVariable |
Avoid variables with short names like LF |
3 |
85 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
126 |
ShortVariable |
Avoid variables with short names like b |
3 |
130 |
ShortVariable |
Avoid variables with short names like u |
3 |
137 |
ShortVariable |
Avoid variables with short names like l |
3 |
138 |
ShortVariable |
Avoid variables with short names like b |
3 |
162 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
164 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
206 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
216 |
ShortVariable |
Avoid variables with short names like b |
3 |
223 |
ShortVariable |
Avoid variables with short names like b |
3 |
241 |
ShortVariable |
Avoid variables with short names like b |
3 |
261 |
ShortVariable |
Avoid variables with short names like b |
3 |
284 |
UnnecessaryModifier |
Unnecessary modifier 'final' on method 'encodeQuotedPrintable': private methods cannot be overridden |
3 |
284–291 |
ShortVariable |
Avoid variables with short names like b |
3 |
304 |
ShortVariable |
Avoid variables with short names like b |
3 |
318 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
325 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
330 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
427 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
430 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
469 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
490 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
525 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
528 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
574 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
597 |
org/apache/commons/codec/net/RFC1522Codec.java
Rule |
Violation |
Priority |
Line |
CommentDefaultAccessModifier |
To avoid mistakes add a comment at the beginning of the RFC1522Codec constructor if you want a default access modifier |
3 |
60–62 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
81 |
ShortVariable |
Avoid variables with short names like to |
3 |
88 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
152 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
186 |
org/apache/commons/codec/net/URLCodec.java
Rule |
Violation |
Priority |
Line |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
104 |
ShortVariable |
Avoid variables with short names like b |
3 |
108 |
ShortVariable |
Avoid variables with short names like u |
3 |
113 |
ShortVariable |
Avoid variables with short names like l |
3 |
114 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
137 |
ShortVariable |
Avoid variables with short names like b |
3 |
145 |
FieldDeclarationsShouldBeAtStartOfClass |
Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. |
3 |
171 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
218 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
221 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
243 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
269 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
298 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
301 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
323 |
OnlyOneReturn |
A method should have only one exit point, and that should be the last statement in the method |
3 |
345 |
|