1. findbugs: http://findbugs.sourceforge.net/
Check yourCodeCommon bad practices in: the database has forgotten to close, the stream has forgotten to close, and the name is not standardized... Similar to PMD, but small and fast.
Update site: http://findbugs.cs.umd.edu/eclipse
Usage: Right-click the project and choose "findbugs"
2. Code Analysis Plugin: http://cap.xore.de/
It can display the dependencies between classes and packages in a graphical manner, helping you make better (better encapsulation and reusability) Oo designs. According to the official website, the theoretical basis is a paper by Robert Martin in 1994.Article). Of course, this analysis can only be referred to as a reference. If a good OO design can be analyzed in this way, no architect is required...
Update site: http://cap.xore.de/update
Usage: Right-click a project and choose "show cap"
Speaking of Java code quality check, recently saw a sonar (http://www.sonarsource.org/), has never used, looks good.