Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Cannot resolve dependency (but Activator can)

See original GitHub issue

Running sbt stage against this application has a different result than activator stage: https://github.com/gifman009/Licenta

More information in this thread: https://groups.google.com/forum/#!topic/play-framework/RLSPwvOqBIE

$ sbt stage
...
[warn] ::::::::::::::::::::::::::::::::::::::::::::::
[warn] :: UNRESOLVED DEPENDENCIES ::
[warn] ::::::::::::::::::::::::::::::::::::::::::::::
[warn] :: com.typesafe.sbtrc#client-2-11;0.3.1: not found
[warn] :: com.typesafe.sbtrc#actor-client-2-11;0.3.1: not found
[warn] ::::::::::::::::::::::::::::::::::::::::::::::

$ activator stage
...
[info] downloading https://repo.typesafe.com/typesafe/ivy-releases/com.typesafe.sbtrc/actor-client-2-11/0.3.1/jars/actor-client-2-11.jar ...
[info]     [SUCCESSFUL ] com.typesafe.sbtrc#actor-client-2-11;0.3.1!actor-client-2-11.jar (36444ms)
[info] downloading https://repo.typesafe.com/typesafe/ivy-releases/com.typesafe.sbtrc/client-2-11/0.3.1/jars/client-2-11.jar
[info]     [SUCCESSFUL ] com.typesafe.sbtrc#client-2-11;0.3.1!client-2-11.jar (196692ms)
...
[info] Done packaging.
[success] Total time: 1028 s, completed Jun 11, 2015 4:57:22 PM

If I remove “sbt-fork-run-plugin” from that project, then it resolves the sbtrc dependencies. https://github.com/gifman009/Licenta/blob/master/project/play-fork-run.sbt

I’m not sure if this is an Activator or SBT bug.

Issue Analytics

State:
Created 8 years ago
Comments:7 (2 by maintainers)

Top GitHub Comments

11reactions

vromancascommented, Nov 20, 2015

Removing the project/sbt-ui.sbt file and the fork in run := true entry from the build.sbt file fixed the problem for me

7reactions

jkutnercommented, Jul 14, 2015

I found that adding the following to the build.sbt resolves the dependency:

resolvers += Resolver.url("Typesafe Ivy releases", url("https://repo.typesafe.com/typesafe/ivy-releases"))(Resolver.ivyStylePatterns)

I’m not sure why the ivyStylePatterns is required. The problem is that when the build runs with the plugin, it needs the extra resolve. I don’t think it’s possible to add the resolver from the plugin though.

I believe this is the same issue discussed here: http://stackoverflow.com/questions/30248497/is-it-possible-to-add-a-resolver-to-an-sbt-projects-build-via-an-autoplugin

So this may turn from a bug to feature request.

Top Results From Across the Web

SBT: cannot resolve dependency that used to work before

1 Answer 1 ... If you are in sbt console, just run reload command and try again. After you update your dependencies or...

Cannot resolve dependencies... - Optimizely World

First, compare the assembly redirects in web.config so that they point to the same versions as in the working project. If still no...

Idea can't resolve local maven dependencies in WSL2

We have a multi-module Maven project where individual modules are interconnected and use each other as dependency. We never had issue with this...

Dependency injection - .NET | Microsoft Learn

When services are resolved by ActivatorUtilities , constructor injection requires that only one applicable constructor exists. Constructor ...

Dependency issue issue with Mule EE 3.7.2 maven application.

... to execute goal on project trial: Could not resolve dependencies for project com.mycompany:trial:mule:1.0.0-SNAPSHOT: Failed to collect dependencies at ...