This sometimes happens if you compile huge codebases – a lot of classes get loaded into the VM running sbt. You need to increase the PermGen space for sbt – use the flag -XX:MaxPermSize=256m, where 256 you can change with the desired size of the permanent generation. Run: cat `which sbt` to locate you sbt … Read more
This sometimes happens if you compile huge codebases – a lot of classes get loaded into the VM running sbt. You need to increase the PermGen space for sbt – use the flag -XX:MaxPermSize=256m, where 256 you can change with the desired size of the permanent generation. Run: cat `which sbt` to locate you sbt … Read more
With the help from sbt mailing list, I was able to create a solution as follows: def publishSnapshot = Command.command(“publish-snapshot”) { state => val extracted = Project extract state import extracted._ val eVersion = getOpt(version).get // getting current version runTask(publish in Compile, append(Seq(version := “newVersion”), state), true ) state }
I had the same issue. This solution worked me everytime. 1. Click on sbt tab of right side in IntelliJ Idea 2. Click on Refresh symbol It will revalidate the Local cache and Gradle dependencies. That’s it.
Spark 2.1.0 contains com.fasterxml.jackson.core as transitive dependency. So, we do not need to include then in libraryDependencies. But if you want to add a different com.fasterxml.jackson.core dependencies’ version then you have to override them. Like this: name := “testSpark2” version := “1.0” scalaVersion := “2.11.8” dependencyOverrides += “com.fasterxml.jackson.core” % “jackson-core” % “2.8.7” dependencyOverrides += “com.fasterxml.jackson.core” … Read more
You need the following on your build.sbt file. javacOptions ++= Seq(“-source”, “1.8”, “-target”, “1.8”, “-Xlint”) initialize := { val _ = initialize.value val javaVersion = sys.props(“java.specification.version”) if (javaVersion != “1.8”) sys.error(“Java 1.8 is required for this project. Found ” + javaVersion + ” instead”) }
LCartwright is correct that this is due to the SHA-1 hash file differring from the hash of the POM on maven central. To get around this you can add the JBoss maven repository, where the hash matches, to your resolvers in the global sbt config ~/.sbt/0.13/global.sbt resolvers += “JBoss” at “https://repository.jboss.org/”
To fix this, remove the folder .idea and reimport the project. The root cause remains a mystery…
You can use eval at the sbt prompt with the appropriate system properties: > eval System.getProperty(“java.version”) [info] ans: String = 1.7.0_45 > eval System.getProperty(“java.home”) [info] ans: String = /Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home/jre (The other answers are fine too, this is just another method.)
It should already be the case in 0.12 that you can put .sbt files in the base directory of a subproject and the settings there will be included in that project’s scope. Code is reused between .sbt files by creating a normal .scala file in project/. The code in project/ will be available for use … Read more