CODEWITHSUNDEEP
scalasbt
Andrew Bucknell
Andrew Bucknell

Reputation: 1950

In SBT 1.3.8 how can I figure out who is bringing in a dependency?

When I start an app using sbt jetty:quickstart I get a container initialisation error. I think this is because my app is bringing in an old servlet instance. I dont explicitly mention this dependency.

I've found file:/C:/Users/drewb/AppData/Local/Coursier/cache/v1/https/repo1.maven.org/maven2/javax/servlet/servlet-api/2.5/servlet-api-2.5.jar on my classpath for jetty:quickstart and I guess this is causing the error. I am trying to figure out how I can identify who is bringing in this dependency so I can get rid of it.

In SBT 1.3.8 how can I figure out who is bringing in a dependency? Because sbt-dependency-graph doesnt work with 1.3.x Im looking for an alternative - hopefully the sbt team had something in mind.

Upvotes: 3

Views: 1066

Answers (2)

Andrew Bucknell
Andrew Bucknell

Reputation: 1950

I couldn't make this work with sbt 1.3.8. I dropped back to 1.2.8 and wound up using coursierDependencyTree with the coursier plugin. addSbtPlugin("io.get-coursier" % "sbt-coursier" % "2.0.0-RC6-1") https://get-coursier.io/docs/sbt-coursier

Upvotes: 1

QuickSilver
QuickSilver

Reputation: 4045

I have used sbt-dependency-graph for dependency hierarchy look up

https://github.com/jrudolph/sbt-dependency-graph

Upvotes: 0

Related Questions