"javac returned nonzero exit code" in sbt 0.13.8

[Art O]

I note the interface to javac changed in sbt 0.13.8 (https://github.com/sbt/sbt/pull/1702)

This seems to have had the unfortunate side-effect that the details of (some) compilation errors in Play applications are not being reported (e.g. file name, line number) which makes fixing them impossible. For example if you mis-spell a route, you just get

[error] (compile:compileIncremental) javac returned nonzero exit code

and nothing in the logs.

Is there some config option to enable verbose compilation that I'm missing? I'm using Play Java 2.4.2, but the problem is also in Play 2.3 if you use sbt 0.13.8.

Regards

Art

[Art O]

On Monday, July 27, 2015 at 10:41:24 AM UTC+1, Art O wrote:

This seems to have had the unfortunate side-effect that the details of (some) compilation errors in Play applications are not being reported (e.g. file name, line number) which makes fixing them impossible. For example if you mis-spell a route, you just get

[error] (compile:compileIncremental) javac returned nonzero exit code

Replying to my own message to clarfiy: I've just discovered that removing "-Xlint" from the javacOptions fixes this problem, though obviously now I can't use that somewhat useful compiler flag. 

[Naftoli Gugenheim]

Sounds like a bug in SBT

--
You received this message because you are subscribed to the Google Groups "play-framework" group.
To unsubscribe from this group and stop receiving emails from it, send an email to play-framewor...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/play-framework/ced56f2b-72a0-4b70-9ae8-9ad29ed2ba34%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.