The conflicts appear because: you’ve specified your Scala version to be 2.11 you’ve explicitly specified the Scala version (2.10) for the reactivemongo and poi-scala libraries. The fix is to use the %% operator for those two libraries as well. “org.reactivemongo” %% “reactivemongo” % reactiveMongoVersion, “info.folone” %% “poi-scala” % foloneVersion That’s the purpose of the %% … Read more
Here’s what I did (sbt 0.13 + artifactory – setup should be similar for nexus): 1) Edited the file ~/.sbt/repositories as specified here: http://www.scala-sbt.org/0.13.0/docs/Detailed-Topics/Proxy-Repositories.html [repositories] local my-ivy-proxy-releases: http://repo.company.com/ivy-releases/, [organization]/[module]/(scala_[scalaVersion]/)(sbt_[sbtVersion]/)[revision]/[type]s/[artifact](-[classifier]).[ext] my-maven-proxy-releases: http://repo.company.com/maven-releases/ 2) Locked down my artifactory to disable anonymous access. 3) Created a credentials file in ~/.sbt/.credentials realm=Artifactory Realm host=artifactory.mycompany.com user=username password=password 4) Created a … Read more
I figured it out. Once I knew that the -d flag would tell me what settings SBT was actually using, I saw that the values in my SBT_OPTS environment variable were being clobbered by other, lower settings. Where were those coming from? From my JAVA_OPTS env variable! I should have noticed them sooner, but now … Read more
When you write small programs that consist of only one, or just two or three source files, then it’s easy enough to compile those source files by typing scalac MyProgram.scala in the command line. But when you start working on a bigger project with dozens or maybe even hundreds of source files, then it becomes … Read more
There is a difference between standalone and making a project useable as a dependency or another project. In the first case, you would use a plugin such as sbt-assembly. What it will do is create one jar file containing the project class files along with all of its dependencies. If you write an application, what … Read more
I’ve come up with a working solution for Scala 2.13.7 (no need for any plugin) for Play 2.8.11. Take a look on those examples and adjust to your needs: scalacOptions ++= Seq( “-Wconf:cat=unused-imports&site=.*views.html.*:s”, // Silence import warnings in Play html files “-Wconf:cat=unused-imports&site=<empty>:s”, // Silence import warnings on Play `routes` files “-Wconf:cat=unused-imports&site=router:s”, // Silence import warnings … Read more
In Menu: View -> Tool Windows there should be two entries: SBT SBT Console The first you can use to refresh IDEA project structure from SBT and view dependencies. The second gives you a console where you can run sbt commands. Update: As Justin already aded: As of IntelliJ IDEA 2017.1 Build #IC-171.3780.52 there is … Read more
Heiko’s approach will probably work, but will lead to none of the dependencies of the 3rd party lib to be downloaded. If you only want to exclude a specific one use exclude. libraryDependencies += “foo” % “bar” % “0.7.0” exclude(“org.baz”, “bam”) or … excludeAll( ExclusionRule(organization = “org.baz”) ) // does not work with generated poms!
To refresh IntelliJ after changes made in *.sbt files: Open the SBT Project pane (Menu View / Tool WIndows / SBT) Right click on your SBT project Select Refresh external project
Run sbt commons/test. See detailed explanation in Scopes. You may also use the combination of two commands from sbt – changing the current project using project and executing test afterwards. sbt “project commons” test You can also use sbt “; project commons; test”