Jan Christopher Vogt

will look into the crash now :)

Getting closer. This seems be be caused by cbt itself using an older Scala version (2.11.8) than one of the dependencies of the plugin (2.11.11). We could temporarily fix this...

btw. the way I found out is by printing the classloader in the top line of cbt in the StackTrace of the crash. `Lib.scala:70`

While I am still working on a more permanent fix, if you rebase your PR on this one: https://github.com/cvogt/cbt/pull/560 you should be unblocked. Upgrading scala to 2.11.11 solved the problem...

(#560 currently fails the build, but don't worry about that. It looks like it only affect cross-cbt-version integration, which shouldn't block you here and I'll look into as well)

current dependencies, that would need to be made optional or ported to Scala Native: dependencies: - scala.xml - "org.eclipse.jgit", "org.eclipse.jgit", "4.2.0.201601211800-r" on OSX for native file change watching - jna...

for git, we may be able to just drop in the command line tool instead of jgit

https://facebook.github.io/watchman/docs/install.html may allow replacing barbary watch service by combining cbt with an external tool rather than letting it be aware of file watching see https://gitter.im/cvogt/cbt?at=579787637c9324e20effd586

Currently the workaround is calling cbt tasks that require this via the `direct` meta task, e.g. `cbt direct publishSigned`, so that java.io.Console is available.

We may be able to use System.in instead of console