fedesilva

I think that you will have to keep that sbt line there because akka-actor comes with the distribution but is a separate jar. So you will have to pull that dependency yourself in sbt.

"For Akka users this change does not have visible effects (you will continue to depend on the same artifacts)" http://letitcrash.com/post/37716546018/2-1-spotlight-akka-ac...

Not likely to be fixed any time soon. Does incremental compile not help?

Can you provide more info?

I have 2 scala programs in production, one of which also has one java file (merssenetwister inlined) and I deploy incrementally built jars without any problems so far.

What scala+sbt versions (or whatever) do you use?

(editted formatting)

Thank you, Sir. This tip made my day.

While I do not care for obfuscation for its IP protection function, having the source visible and accessible is a problem for games: how can we know that top scores are valid and a variable has not been modified? Basically, all JS games are cheatable. John Resig talked about this http://bit.ly/bO3bcf

I wonder if this kind of ... "homage" is what made him vanish.

Mine in F#