No, you cannot do this. The way to do it is as you described. Then, whenever you make changes to build.sbt (e.g., new jar dependency), rerun the eclipse command from sbt and refresh the project in Eclipse so that the newly generated files are reloaded.
Did you create a assembly.sbt at the root of your project? Alongside your build.sbt? If so, then that’s the problem. You want to have it inside the project directory. Having done that it worked out the box as expected with the rest of your setup: > assembly [info] Including: scala-library.jar [info] Checking every *.class/*.jar file’s … Read more
There are many plugins you can use: sbt-assembly, sbt-proguard, sbt-onejar, xitrum-package etc. See the list of SBT plugins.
I think you can apply a setting across projects using scope ThisBuild, like parallelExecution in ThisBuild := false I don’t know if you can combine that with scope Test, but it might not be necessary.
I had the same problem, I’m using the assembly plugin. In this case, the solution was to modify the build file and add test in assembly := {}
“org.apache.hbase” % “hbase” % “0.90.4” % “test” classifier “tests”
Did you try make-pom from sbt? It generates basic POM for the current project at the ./target. To customize generation, you can override pomExtra, pomIncludeRepository and pomPostProcess at the project definition.
Add the following settings to the Play project: sources in (Compile,doc) := Seq.empty publishArtifact in (Compile, packageDoc) := false With the change it should be as follows: play.Project(appName, appVersion, appDependencies) .settings(scalaVersion := “2.10.3”) .settings(jsSettings : _*) .settings( publishArtifact in (Compile, packageDoc) := false, publishArtifact in packageDoc := false, sources in (Compile,doc) := Seq.empty ) Thanks … Read more
you can use dependencyOverrides: dependencyOverrides += “foo” %% “foo” % “1.2.2” You’re not avoiding “logical inconsistencies” anyway. If you force a version, you have to manually take care of compatibility with other libraries, there’s no way out of that. From the documentation: Overriding a version For binary compatible conflicts, sbt provides dependency overrides. They are … Read more
The sbt.ivy.home property is only half of the solution. It controls where the sbt launcher downloads sbt itself (and related dependencies like the scala compiler and library, etc.) As noted by Joachim Hofer, it has no effect on where the dependencies declared by your project get downloaded. To change that location, you must set the … Read more