Searching repository for plugin with prefix: 'scala'. If you installed something in the system, most probably this is irrelevant for sbt builds.$> mvn scala:compile -Ddispla圜md=true -DrecompileMode=all If you're using sbt, most probably you will not need to install anything in your system (except sbt and Java). "org.scalanlp" %% "breeze-natives" % "1.0" cross CrossVersion.for3Use2_13,īut before Breeze 1.0 there was no Scala-2.13 version, so you can use only Scala 2.10-2.12 with them scalaVersion := "2.12.17" "org.scalanlp" %% "breeze" % "1.0" cross CrossVersion.for3Use2_13, "org.scalanlp" %% "breeze-natives" % "2.1.0",įor Breeze 1.x there is no Scala-3 version but there is Scala-2.13 version, so you can try compatibility mode scalaVersion := "3.2.2" So try the following build.sbt scalaVersion := "3.2.2" They are published for Scala 3 since Breeze 2.0 As you can see, Breeze and Breeze-natives 0.11.2 were published for Scala 2.10, 2.11. You're using quite old versions of your dependencies. There is compatibility mode CrossVersion.for3Use2_13/ CrossVersion.for2_13Use3 But there is Scala 2.13 - Scala 3 interop Not all of them can be easily migrated into Scala 3 (because of Scala 2 macros etc.). Not all dependencies are published for Scala 3. Scala 3 is still quite new version of Scala. This is using a build tool like Sbt, Mill, Fury, Cbt in Scala, Maven or Gradle in Java, Bazel in Java/C++/Go, Pants in Python/Go/Java/Scala/Kotlin, Make in C++, Pip in Python, Cabal or Stack in Haskell etc. There is no sandboxing here in Docker sense, you're not creating an isolated environment commented that this can be considered as sandboxing in the sense that sbt manages dependencies itself, rather than relies on the ones installed systemwide). So why is it that build.sbt cannot resolve the dependencies for a more recent scala version? Or, should it?įurther, if I want to work on the same project with the newer scala version, should I do it without sbt, and somehow installing the dependencies at the system level, available to all projects? How do I go around it?Ĭan I think of the build.sbt as a form of Dockerfile, that can take care of the dependencies on any host by creating its own sandbox? not found: /home/della/.ivy2/localorg.scalanlp/breeze_3/0.11.2/ivys/ivy.xml : Error downloading org.scalanlp:breeze_3:0.11.2 Scala code runner version 3.2.2 - Copyright 2002-2023, ~/s/l/s/chap02 (master)> sbt -versionīut changing it to 3.2.2 results in the following stack-trace (just the top part). But I wanted to match it to my system scala version (see below for the version details). ![]() ![]() The repo itself uses scalaVersion := "2.11.7" which works fine. ![]() work is not entirely clear to me yet, but can I think of the build.sbt as a form of Dockerfile, that can take care of the dependencies on any host by creating its own sandbox? ![]() "org.scalanlp" %% "breeze-natives" % "0.11.2",īeing new to scala from python and C++, the idea of how different scala environments, dependencies etc. Learning Scala from the Scala for Data Science book and the companion Github repo, here I am particularly talking about the build file for Chapter 2, copied below (with minor modification) for reference.
0 Comments
Leave a Reply. |