Name | Checked | Synopsis |
---|
Naming1
|
 |
Avoid variables with short names |
Naming2
|
 |
Avoid excessively long variable names |
Naming3
|
 |
Avoid using short method names |
Naming4
|
 |
Use naming conventions for variables |
Naming5
|
 |
Method name does not begin with a lower case character |
Naming6
|
 |
Class names should begin with an uppercase character |
Naming7
|
 |
Abstract classes should be named 'AbstractXXX' |
Naming8
|
 |
Avoid using dollar signs in variable/method/class/interface names |
Naming9
|
 |
Classes should not have non-constructor methods with the same name as the class |
Naming10
|
 |
The method name and return type are suspiciously close to hashCode() |
Naming11
|
 |
The field name indicates a constant but its modifiers do not |
Naming12
|
 |
The method name and parameter number are suspiciously close to equals(Object) |
Naming13
|
 |
It is somewhat confusing to have a field name matching the declaring class name |
Naming14
|
 |
It is somewhat confusing to have a field name with the same name as a method |
Naming15
|
 |
Don't define methods with the same name as the class name |
Naming16
|
 |
All classes and interfaces must belong to a named package |
Naming17
|
 |
Package name contains upper case characters |
Naming18
|
 |
Avoid naming non-fields with a member-like prefix |
Naming101
|
 |
Treat acronyms as words |