There’s a very convenient -jvm-debug flag in the official SBT packages for Mac, Linux & Windows. You can use the flag to specify the debug port: sbt -jvm-debug 5005 Under the covers, this starts the JVM for SBT with the typical verbose debugging incantation: -Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005 You now can run your code as normal, for … Read more
sbt –version It now works as of version 1.3.3+ (credit to @ElectronWill). You may also want to use sbt about that (copying Mark Harrah’s comment): The about command was added recently to try to succinctly print the most relevant information, including the sbt version.
There are three basic ways how to create a project – modern versions of IntelliJ can import sbt project out of the box, otherwise you can either use sbt plugin to generate IntelliJ project, or use IntelliJ Scala plugin to create sbt project. Basic features work out of the box using both solutions, some complex … Read more
Add the following code to your build.sbt file: assemblyMergeStrategy in assembly := { case PathList(“META-INF”, _*) => MergeStrategy.discard case _ => MergeStrategy.first }
We’re using Maven to build Scala projects at work because it integrates well with our CI server. We could just run a shell script to kick off a build, of course, but we’ve got a bunch of other information coming out of Maven that we want to go into CI. That’s about the only reason … Read more
Resources are meant to be accessed using the special getResource style methods that Java provides. Given your example of data.xml being in $SBT_PROJECT_HOME/src/test/resources/, you can access it in a test like so: import scala.io.Source // The string argument given to getResource is a path relative to // the resources directory. val source = Source.fromURL(getClass.getResource(“/data.xml”)) Of … Read more
From the official documentation: http://www.playframework.com/documentation/2.1.1/SBTDependencies Getting the right Scala version with %% If you use groupID %% artifactID % revision instead of groupID % artifactID % revision (the difference is the double %% after the groupID), SBT will add your project’s Scala version to the artifact name. This is just a shortcut. You could write … Read more
sbt shell While in sbt shell (if you don’t want to change your build.sbt): $ sbt > set ThisBuild/scalacOptions ++= Seq(“-unchecked”, “-deprecation”) > compile > exit Due to in ThisBuild, set applies the settings to all sub-projects, as well. Command Line You could also run the above as a single command on command line. sbt … Read more
This is now supported (since ScalaTest 2.1.3) within interactive mode: testOnly *MySuite — -z foo to run only the tests whose name includes the substring “foo”. For exact match rather than substring, use -t instead of -z. If you run it from the command line, it should be as single argument to sbt: sbt ‘testOnly … Read more
$ sbt –version Now works as of version 1.3.3+ (credit to @ElectronWill). You may also want to use sbt about that (copying Mark Harrah’s comment): The about command was added recently to try to succinctly print the most relevant information, including the sbt version.