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.

Fix or document `sbt test`

See original GitHub issue

Following the discussion in Gitter.

Currently it fails with:

sbt.ResolveException: unresolved dependency: com.typesafe.play#play-json_2.12;2.3.10: not found
unresolved dependency: io.argonaut#argonaut_2.12;6.1: not found
unresolved dependency: io.github.netvl.picopickle#picopickle-core_2.12;0.2.1: not found
unresolved dependency: io.github.netvl.picopickle#picopickle-backend-jawn_2.12;0.2.1: not found
...
sbt.ResolveException: unresolved dependency: com.typesafe.akka#akka-actor_2.12;2.3.9: not found
unresolved dependency: io.spray#spray-httpx_2.12;1.3.3: not found
unresolved dependency: io.spray#spray-routing-shapeless2_2.12;1.3.3: not found
unresolved dependency: io.spray#spray-testkit_2.12;1.3.3: not found

Issue Analytics

State:
Created 7 years ago
Comments:7 (6 by maintainers)

Top GitHub Comments

1reaction

jensraabycommented, Dec 19, 2016

I’ve tried swapping some of the libraries in question to 2.12-compatible versions, and hardcoding the picopickle version to 2.11, but that then causes other issues:

-      "com.typesafe.play" %% "play-json" % "2.3.10",
-      "io.argonaut" %% "argonaut" % "6.1",
+      "com.typesafe.play" %% "play-json" % "2.6.0-M1",
+      "io.argonaut" %% "argonaut" % "6.2-RC2",
       "io.spray" %% "spray-json" % "1.3.2",
-      "io.github.netvl.picopickle" %% "picopickle-core" % "0.2.1",
-      "io.github.netvl.picopickle" %% "picopickle-backend-jawn" % "0.2.1",
+      "io.github.netvl.picopickle" % "picopickle-core_2.11" % "0.3.1",
+      "io.github.netvl.picopickle" % "picopickle-backend-jawn_2.11" % "0.3.1",
       "org.scalatest" %% "scalatest" % scalaTestVersion % "test",

Result in IntelliJ:

[info] Set current project to circe (in build file:/Users/raabyj01/Projects/circe/circe/)
[error] Modules were resolved with conflicting cross-version suffixes in {file:/Users/raabyj01/Projects/circe/circe/}benchmark:
[error]    com.chuusai:shapeless _2.12, _2.11
[error]    org.spire-math:jawn-parser _2.12, _2.11
[error]    org.typelevel:macro-compat _2.12, _2.11
[trace] Stack trace suppressed: run 'last benchmark/*:update' for the full output.
[error] (benchmark/*:update) Conflicting cross-version suffixes in: com.chuusai:shapeless, org.spire-math:jawn-parser, org.typelevel:macro-compat

0reactions

travisbrowncommented, Feb 23, 2017

@worldwar2008 Do you have an explicit dependency on Shapeless (specifically on an earlier version than circe’s 2.3.2)?

Top Results From Across the Web

Testing Scala with sbt and ScalaTest on the Command Line

The project comes with ScalaTest as a dependency in the build.sbt file. cd into the directory and run sbt test . This will...

sbt Reference Manual — Testing sbt plugins

The scripted test framework is used to verify that sbt handles cases such as that described above. The framework is made available via...

ScalaTest in sbt: is there a way to run a single test without tags?

This is now supported (since ScalaTest 2.1.3) within interactive mode: testOnly *MySuite -- -z foo. to run only the tests whose name includes...

Is it possible to only show the errors when executing tests from ...

failed tests of this second module are printed at the very end of the log. See https://travis-ci.org/nlochschmidt/scalatest-sbt-output/builds/32703529. Having ...

Tutorial · Scalafix - Scala Center

This starts an sbt shell session from where you can run the test suite with tests/test . Optionally, if you use IntelliJ, import...