You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert
% sbt clean run ++2.11.12 ... [info] Loading project definition from .../project [info] Loading settings from build.sbt ... [info] Set current project to projwithsub (in build file:.../) [success] Total time: 0 s, completed Mar 5, 2018 4:23:14 PM [info] Updating ... [info] Done updating. [info] Compiling 1 Scala source to .../target/scala-2.12/classes ... [info] Done compiling. [info] Packaging ..
Adding a "compile"-scoped dependency to a subproject puts the dependent classes not only on the source path of scalac but also on the class path so that macros can be found. But this only works for classes, not for resources, e.g. reference.conf for Typesafe config. sbt should treat resources the same as classes for the compiler classpath, like in other dependency management scenarios. Here's a br
I'm trying to migrate from sbt-doge to SBT 1.0, but I can't find a way to replace strict aggregation (+++). Using it seems to be the only way to build a project for a specific version (a thing usually done in Travis builds) in typical setups of a root project aggregating all sub-projects. I think that the default behavior of ++ should be to do strict aggregation as I find it difficult to imagine a
Although sbt adds the target directory to the classpath of the compiler, this causes problems if the compiler needs access to resources because they are only copied AFTER (or in parallel with) the compile. Therefore you can get a situation where compile fails the first time, then succeeds. To avoid this, I recommend that resources are copied BEFORE compilation. Original report below, which slightl
[default-tests-sbt] $ /usr/lib/jvm/java-8-oracle/bin/java -Dsbt.log.noformat=true -Xmx2G -jar /var/lib/jenkins/tools/org.jvnet.hudson.plugins.SbtPluginBuilder_SbtInstallation/SBT_default_launcher/bin/sbt-launch.jar clean test:clean buildUmp test [info] Loading project definition from /var/lib/jenkins/workspace/default-tests-sbt/project [info] Set current project to ump (in build file:/var/lib/jenk
Add operations like map, flatMap which assume right-bias Deprecate {Left,Right}Projection Deprecate left and right in favor of swap Add contains, toOption, toTry, toSeq and filterOrElse toSeq returns collection.immutable.Seq instead of collection.Seq Don't add get There are no incompatible changes. The only possibility of breakage that exists is when people have added extension methods named map,
We are very pleased to announce the availability of Scala 2.11.6! Get started with the Hello Scala 2.11 template in Typesafe Activator Download a distribution from scala-lang.org Obtain it via Maven Central Scala 2.11.6 is a bugfix release that is binary compatible with previous releases in the Scala 2.11 series. We would like to highlight the following changes: We fixed a cross-site scripting vul
% sbt [info] Loading global plugins from /home/smarter/.sbt/0.13/plugins [info] Updating {file:/home/smarter/.sbt/0.13/plugins/}global-plugins... [info] Resolving org.fusesource.jansi#jansi;1.4 ... [info] Done updating. [info] Loading project definition from /home/smarter/opt/dotty/project [info] Updating {file:/home/smarter/opt/dotty/project/}dotty-build... [info] Resolving org.fusesource.jansi#j
[info] Packaging C:\[…]\projectName.jar ... [error] java.io.IOException: CreateFile() failed with error 3 [error] at sbt.internal.io.WinMilli$.getHandle(Milli.scala:275) [error] at sbt.internal.io.WinMilli$.getModifiedTimeNative(Milli.scala:281) [error] at sbt.internal.io.WinMilli$.getModifiedTimeNative(Milli.scala:259) [error] at sbt.internal.io.MilliNative.getModifiedTime(Milli.scala:66) [error]
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く