The last workable option.
my_project \ build.sbt looks like this:
name := "my_project" organization := "my.app" version := "1.0" scalaVersion := "2.10.2" resolvers ++= Seq[sbt.Resolver]( "Local Maven Repository@wildfly " at "file:///M:/", "Local Maven Repository@common " at "file:///" + Path.userHome.absolutePath + "/.m2/repository" ) seq(webSettings :_*) ... libraryDependencies += ...
C: \ Users \ svc \ .sbt \ repositories - deleted
Posted by sbt-launch.jar in C: \ Program Files (x86) \ sbt \ bin
Posted by build.properties in the my_project / project folder with this line inside:
sbt.version=0.13.6
(which version does not matter, it works with any version 0.13. ~ - I checked)
Placed plugins.sbt in the folder C: \ Users \ svc.sbt \ 0.13 \ plugins with these lines inside:
resolvers += "typesave" at "http://repo.typesafe.com/typesafe/releases" addSbtPlugin("com.typesafe.sbteclipse" % "sbteclipse-plugin" % "2.3.0") addSbtPlugin("com.earldouglas" % "xsbt-web-plugin" % "0.4.2")
Deleted C: \ Users \ svc \ .sbt \ 0.13.5
Placed sbtconfig.txt in the C: \ Program Files (x86) \ sbt \ conf directory with these lines inside:
# Set the java args to high -Xms1G -Xmx2G -XX:MaxPermSize=512m -XX:ReservedCodeCacheSize=128m # Set the extra SBT options -DproxySet=true -Dsbt.log.format=true #-Dhttp.proxyHost=my-proxy-in.com #-Dhttp.proxyPort=8080 #-Dhttps.proxyHost=my-proxy-in.com #-Dhttps.proxyPort=8080 #-Dhttp.proxyUser=my_user #-Dhttp.proxyPassword="my_psw" -Dhttp.proxyHost=my-proxy-out.com -Dhttp.proxyPort=8080 -Dhttps.proxyHost=my-proxy-out.com -Dhttps.proxyPort=8080
In the case of some artifacts placed on a corporate closed network (as for me), you have to run sbt twice - with two different proxies (comments / no comments).
source share