From http://books.sonatype.com/mvnex-book/reference/optimizing-sect-dependency-plugin.html <http://books.sonatype.com/mvnex-book/reference/optimizing-sect-dependency-plugin.html>
"A good rule of thumb in Maven is to always declare explicit dependencies for classes referenced in your code.” From time to time I run dependency:analyze -DignoreNonCompile=true -DoutputXML=true > On 18 Jan 2018, at 07:31, Debraj Manna <subharaj.ma...@gmail.com> wrote: > > Cross-posting from stackoverflow > <https://stackoverflow.com/questions/48315863/how-does-mvn-dependencyanalyze-work> > > Can someone let me know how does mvn dependency:analyze work ? An output of > mvn > dependency:analyze in one of my project shows > > [WARNING] Used undeclared dependencies found:[WARNING] > org.apache.commons:commons-lang3:jar:3.4:compile[WARNING] > com.fasterxml.jackson.core:jackson-annotations:jar:2.8.0:compile...[WARNING] > Unused declared dependencies found:[WARNING] > org.springframework.boot:spring-boot-starter-test:jar:1.5.4.RELEASE:test[WARNING] > > org.springframework.restdocs:spring-restdocs-mockmvc:jar:1.1.3.RELEASE:test[WARNING] > ch.qos.logback:logback-classic:jar:1.1.11:compile > > Can some one let me know the following - > > - What does Used undeclared dependencies found denote? Does it mean that > this is not declared in pom.xml dependencies but getting used in code > and is included via some transitive dependencies? > - Does Unused declared dependencies found check only for the > dependencies declared > in pom.xml or it checks transitive dependencies as well? > > Maven Version - 3.5.0
