deadcode4j helps you find code that is no longer used by your application. It is especially useful for cleaning up legacy code.
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
config
src
tools
.gitignore
.travis.yml
README.md
license.txt
pom.xml

README.md

deadcode4j Latest version Build Status Coverage Status

Join the chat at https://gitter.im/ImmobilienScout24/deadcode4j

deadcode4j helps you find code that is no longer used by your application. It is especially useful for cleaning up legacy code.

As deadcode4j is available via the Maven repository, you can simply run
mvn de.is24.mavenplugins:deadcode4j-maven-plugin:find -Dmaven.test.skip=true
to analyze your project.
deadcode4j will trigger the package phase to be executed for a project (and for all modules listed in a reactor project) before analyzing the output directories. The output will look something like this:

[INFO] --- deadcode4j-maven-plugin:2.1.0:find (default-cli) @ someProject ---
[INFO] Analyzed 42 class(es).
[WARNING] Found 2 unused class(es):
[WARNING]   de.is24.deadcode4j.Foo
[WARNING]   de.is24.deadcode4j.Bar

Have a look at the wiki to get to know the features, read about the available goals, understand the configuration or learn deadcode4j's history and principles.

deadcode4j is tested with Maven 3.0.5, 3.1.1, 3.2.5 & 3.3.9.