Fix sbt deprecation warnings

[krasserm]

[warn] /eventuate/project/ProjectSettings.scala:81: `<<=` operator is deprecated. Use `key := { x.value }` or `key ~= (old => { newValue })`.
[warn] See http://www.scala-sbt.org/0.13/docs/Migrating-from-sbt-012x.html
[warn]     createHeaders in IntegrationTest <<= (createHeaders in IntegrationTest) triggeredBy (createHeaders in Test),
[warn]                                      ^
[warn] /eventuate/project/ProjectSettings.scala:82: `<<=` operator is deprecated. Use `key := { x.value }` or `key ~= (old => { newValue })`.
[warn] See http://www.scala-sbt.org/0.13/docs/Migrating-from-sbt-012x.html
[warn]     compile in IntegrationTest <<= (compile in IntegrationTest) triggeredBy (compile in Test),
[warn]                                ^
[warn] /eventuate/project/ProjectSettings.scala:83: `<<=` operator is deprecated. Use `key := { x.value }` or `key ~= (old => { newValue })`.
[warn] See http://www.scala-sbt.org/0.13/docs/Migrating-from-sbt-012x.html
[warn]     test in IntegrationTest <<= (test in IntegrationTest) triggeredBy (test in Test),
[warn]                             ^
[warn] /eventuate/project/ProjectSettings.scala:89: `<<=` operator is deprecated. Use `key := { x.value }` or `key ~= (old => { newValue })`.
[warn] See http://www.scala-sbt.org/0.13/docs/Migrating-from-sbt-012x.html
[warn]     createHeaders in MultiJvm <<= (createHeaders in MultiJvm) triggeredBy (createHeaders in Test),
[warn]                               ^
[warn] /eventuate/project/ProjectSettings.scala:90: `<<=` operator is deprecated. Use `key := { x.value }` or `key ~= (old => { newValue })`.
[warn] See http://www.scala-sbt.org/0.13/docs/Migrating-from-sbt-012x.html
[warn]     compile in MultiJvm <<= (compile in MultiJvm) triggeredBy (compile in Test),
[warn]                         ^
[warn] /eventuate/project/ProjectSettings.scala:91: `<<=` operator is deprecated. Use `key := { x.value }` or `key ~= (old => { newValue })`.
[warn] See http://www.scala-sbt.org/0.13/docs/Migrating-from-sbt-012x.html
[warn]     executeTests in Test <<= (executeTests in Test, executeTests in MultiJvm) map {
[warn]                          ^
[warn] /eventuate/project/ProjectSettings.scala:182: `<<=` operator is deprecated. Use `key := { x.value }` or `key ~= (old => { newValue })`.
[warn] See http://www.scala-sbt.org/0.13/docs/Migrating-from-sbt-012x.html
[warn]       generateClasspath <<= generateClasspath.dependsOn(sbt.Keys.compile in Test),
[warn]                         ^
[warn] /eventuate/project/ProjectSettings.scala:91: method t2ToTable2 in object Scoped is deprecated: The sbt 0.10 style DSL is deprecated: '(k1, k2) map { (x, y) => ... }' should now be '{ val x = k1.value; val y = k2.value }'.
[warn] See http://www.scala-sbt.org/0.13/docs/Migrating-from-sbt-012x.html
[warn]     executeTests in Test <<= (executeTests in Test, executeTests in MultiJvm) map {
[warn]                              ^
[warn] 8 warnings found

[magro]

I'm just looking at this one. What's weird is that the sbt version from project/build.properties is ignored in my case. My 0.13.12 sbt launcher (Fedora package / rpm) always sets 0.13.12 and also inspect sbtVersion doesn't provide any insights.
However, with sbt -v -sbt-version 0.13.13 sbt is running in fact 0.13.13, so this way I can now reproduce the issue.

Does changing project/build.properties work in your case?

[magro]

AFAICS project/build.properties was broken with the multi-module project (commit 2e97ed2), but I don't understand what's the issue.

[magro]

Ah, found it. A hex dump of build.properties shows that it's starting with ef bb bf, aka byte order mark. Removing this brings build.properties back into play's.

[krasserm]

Good catch, this explains a lot. Thanks for working on it!