errors found in build.sbt are reported with no position (java.lang.ArrayIndexOutOfBoundsException: -1)

This build.sbt:

lazy val bob = scala.Console println

Will crash sbt with no indication whatsoever what happened, where or why. (My real one is more than one line.) The expression is valid scala.

[info] Loading project definition from /Users/paulp/scratch/2014-03-12_sbt_1/project
java.lang.ArrayIndexOutOfBoundsException: -1
    at scala.reflect.internal.util.OffsetPosition.column(Position.scala:249)
    at scala.reflect.internal.util.Position$.formatMessage(Position.scala:33)
    at scala.tools.nsc.reporters.ConsoleReporter.printMessage(ConsoleReporter.scala:49)
    at scala.tools.nsc.reporters.ConsoleReporter.print(ConsoleReporter.scala:52)
    at scala.tools.nsc.reporters.ConsoleReporter.display(ConsoleReporter.scala:78)
    at scala.tools.nsc.reporters.AbstractReporter.info0(AbstractReporter.scala:49)
    at scala.tools.nsc.reporters.Reporter$$anonfun$error$1.apply$mcV$sp(Reporter.scala:70)
    at scala.tools.nsc.reporters.Reporter$$anonfun$error$1.apply(Reporter.scala:70)
    at scala.tools.nsc.reporters.Reporter$$anonfun$error$1.apply(Reporter.scala:70)

The “full log”, or at least it is so implied:

[error] java.lang.ArrayIndexOutOfBoundsException: -1
[error] Use 'last' for the full log.
[debug] > load-failed
[debug] > last
Project loading failed: (r)etry, (q)uit, (l)ast, or (i)gnore?

If the implied empty param list is given, it compiles.

lazy val bob = scala.Console println ()

[paulp]

Your implied crash repro golf challenge does not go unnoticed. 4 chars.

run+

[stillyetanothergithubuser]

Just ran across this error after I accidentally added an “s” after one of 17 dependencies in a 50+ line build.sbt while tabbing through files in my IDE. (So dependency became:, “org.scalaz” %% “scalaz-core” % "7.1.0"s)

It’s not too hard to figure out error is caused by some kind of error in project configuration and back our recent changes to troubleshoot or something like that, but this message seems insanely/aggressively un-userfriendly. If the stack trace could even just include the line that triggered the exception somewhere, it would be far more helpful.