Effective java is a tool to examine your Java codebase. You can use it in three different ways:
- as a Java linter. Just tells it which directory you want to examine, it will spit out a set of warnings and suggestions to improve your code
- run queries from the command line. It could tell you which type of Singleton you are using in your codebase or how many constructors have 10 or more parameters. This modality can be easily integrated with other tools
- run queries interactively. It permits to poke your codebase, parsing it once and running different queries to find out interesting facts about it.
The project is named effectivejava because many queries/checks derive from reading the book Effective Java. Others will be implemented as well (feel free to suggest your favorite ones!).
While reading that book I thought that yes, many principles are well known, but they are rarely applied to a large codebase. I thought that applying them in practice is much harder than it seems, and a tool like this one could help in improving constantly a codebase.
Download the standalone jar from the releases page. No deps needed, everything is packed inside the jar. Feel free to rename it (effectivejava-0.1.0-SNAPSHOT-standalone.jar is a mouthful...)
Just run:
# this generate a jar file
lein jar
# note that 0.1.3 is the current version it could change in the future
java -jar effectivejava-0.1.3-SNAPSHOT-standalone.jar -l -d "<myJavaProjectDir>"You can expect a set of lines like this one:
org.springframework.jdbc.core.SqlInOutParameter : This class has too many constructors (7). Consider using static factory methods or the Builder pattern
If you run this command from the root of your codebase you can avoid the -d option.
Now, suppose you want to know which classes has 5 or more constructor; you can run this command:
java -jar effectivejava-0.1.3-SNAPSHOT-standalone.jar -q mc -d "<myJavaProjectDir>" -t 5You can expect a similar output:
Considering 109 Java files
japa.parser.ast.expr.ArrayCreationExpr : 5
japa.parser.ast.body.MethodDeclaration : 5
japa.parser.ast.body.BaseParameter : 5
japa.parser.ast.body.FieldDeclaration : 5
You can launch interactive mode with the -i option.
java -jar effectivejava-0.1.3-SNAPSHOT-standalone.jar -iA typical interaction could be this one:
> load "."
Loading .
Java files loaded: 440
> mc th 5
Command not implemented: :MC
As you can read from the last line, while the main logic for the interactive mode is there we still miss a few bits :) It will be corrected soon.
I am just getting started so I implemented only a few queries for now:
- mc=many constructors: find the classes which contain the same number of constructors as the given threshold, or more
- mcp=many constructor parameters: find the constructors which contain the same number of parameters as the given threshold, or more
- st=singleton type: find if a type implements the singleton pattern and distinguish between the three types (public field, static factory, singleton enum)
- u=utils classes: find classes having only static methods and verify they have exactly one private constructor taking no parameters
| Item | Status |
|---|---|
| Item 1 | Done |
| item 2 | TODO |
| item 3 | Done |
| item 4 | Done |
| item 5 | TODO |
| item 6 | TODO |
| item 7 | Done |
| item 8 | Planned for v0.2 |
| item 9 | Planned for v0.2 |
| item 10 | Done |
| item 11 | TODO |
| ...item 78 | TODO |
The project is written in Clojure using a java library called JavaParser.
You will need also Leiningen, the build tool for Clojure. It should download also Clojure for you.
To monitor code quality we use kibit and eastwood.
When running eastwood exclude the check for unlimited use of namespaces:
lein eastwood "{:exclude-linters [:unlimited-use]}"
To verify the code is correctly formatted cljfmt is used. You can run it like this:
# to verify possible style issues
lein cljfmt check
# to automatically fix them
lein cljfmt fix
We use lein-ancient to verify our dependencies are up-to-date.
I am reading this book and many advices seem sort of obvious in theory but I guess there are some violations lurking in the large codebase I am working with. I was curious to assess how many violations there were and I needed a way to find them out automatically. And I wanted to learn Clojure. And I had a free sunday. So...
Hope you enjoy this small project of mine. Feel free to open issues and ask questions!
David Ortiz is a regular contributor: he started fixing bugs, setting up Travis and it is contributing many other improvements.
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent