resources.report.rules.pmd.TooManyStaticImports.html Maven / Gradle / Ivy
Go to download
Show more of this group Show more artifacts with this name
Show all versions of sanity4j Show documentation
Show all versions of sanity4j Show documentation
Sanity4J was created to simplify running multiple static code
analysis tools on the Java projects. It provides a single entry
point to run all the selected tools and produce a consolidated
report, which presents all findings in an easily accessible
manner.
TooManyStaticImports
TooManyStaticImports
If you overuse the static import feature, it can make your program unreadable and
unmaintainable, polluting its namespace with all the static members you import.
Readers of your code (including you, a few months after you wrote it) will not know
which class a static member comes from (Sun 1.5 Language Guide).
This rule is defined by the following XPath expression:
.[count(ImportDeclaration[@Static = 'true']) > $maximumStaticImports]
Example:
import static Lennon;
import static Ringo;
import static George;
import static Paul;
import static Yoko; // Too much !
This rule has the following properties:
Name Default value Description
maximumStaticImports
All static imports can be disallowed by setting this to 0