Detecting unused/undeclared dependencies

As your project becomes large and the number of dependencies increase (including transitive dependencies), it is good to know if we have ended up declaring dependencies that we are not using, or if we are using undeclared dependencies (which are brought in by transitive dependencies).

How to do it...

Use the following steps to detect the unused/undeclared dependencies:

1. Run the following Maven command on the demo-selendroid project that we used earlier:

   mvn dependency:analyze
   

2. Note the report generated:

   [WARNING] Used undeclared dependencies found:
   [WARNING]    org.seleniumhq.selenium:selenium-api:jar:2.43.1:compile
   [WARNING]    org.hamcrest:hamcrest-library:jar:1.3:compile
   [WARNING]    io.selendroid:selendroid-common:jar:0.12.0:compile
   [WARNING] Unused declared dependencies found:
   [WARNING]    org.hamcrest:hamcrest-integration:jar:1.3:compile
   

How it works...

As can be seen from the preceding report, Maven has identified a dependency used by the project that...