CODEWITHSUNDEEP
sbt
WestCoastProjects
WestCoastProjects

Reputation: 63162

How to resolve unresolved dependency (with another/latest version perhaps)?

Apparently the version of a transitive dependency within my sbt project has been bumped - but the direct dependency has not "caught up" with that change. 

[error] (*:update) sbt.ResolveException: unresolved dependency: net.sf.py4j#py4j;0.7: not found

The updated (and only available) version is 0.8 (why did they do that is another question.. )

I have attempted to remedy this temporarily by installing the new version into my local maven repo under the old version number of 0.7 - in order to attempt to mollify the dependent library. 

mvn org.apache.maven.plugins:maven-install-plugin:2.5.1:install-file  \
-Dfile=c:\shared\py4j-0.8.1.jar -DgroupId=net.sf.py4j  -DartifactId=py4j -Dversion=version=0.7 -Dpackaging=jar

However, when running sbt yet again, the same error persists. So I need another strategy for dependency resolution.

Upvotes: 0

Views: 273

Answers (1)

Jacek Laskowski
Jacek Laskowski

Reputation: 74709

What about declaring the new version as the dependency in your build and force it (but guess you won't need it as "By default, the latest revision is selected")?

libraryDependencies += "net.sf.py4j" % "py4j" % "0.8" force()

It assumes you've your local Maven repository set up in resolvers - see Resolvers:

sbt can search your local Maven repository if you add it as a repository:

resolvers += "Local Maven Repository" at "file://"+Path.userHome.absolutePath+"/.m2/repository"

Upvotes: 1

Related Questions