On 7 August 2015 at 04:14, James Green <james.mk.gr...@gmail.com> wrote: > See in-line > > On 7 August 2015 at 12:05, Björn Raupach <raupach.bjo...@googlemail.com> > wrote: > >> hi, >> >> > On 07 Aug 2015, at 12:33, James Green <james.mk.gr...@gmail.com> wrote: >> > >> > Hi, >> > >> > I want to know about any imports within our package base that are >> resolved >> > by a transitive dependency. >> > >> > There must be a command or tool for this - I'm not sure I've ever seen >> one >> > though? >> >> Maybe this helps: mvn dependency:resolve >> > > Nope. Allow me to describe my use-case. > > I have been given a source code project. It has a dependency that we have > no clear need for. I remove that dependency. The build now fails because > our sources import something the now-removed dependency transitively > provided. > > I want to know I don't have any other source-code dependencies not listed > in <dependencies>.
Have you looked at Takari ([1])? It enforces stricter rules for dependencies. I have not gotten around to using it yet but I ran into similar problems and this seems like the perfect solution. [1] http://takari.io/book/40-lifecycle.html#enforcing-dependency-usage-during-compilation --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
