Hi all, here is an update on problems found with the new Scala features after releasing 1.3-rc-1:
* Zinc Scala compiler logging is (way) too verbose. This is already fixed in master. * The combination of `useAnt=false` (i.e. Zinc) and `fork=false` doesn't work. I implemented this because there was a concrete need to have (or keep) each of the other three combinations, and it felt a bit strange to leave out the fourth one. I thought that by reusing the InProcessCompilerDaemonFactory we have for Java and Groovy, it would be trivial to implement this. Unfortunately, I forgot to add an integration test for this case. (We are testing quite a few combinations by now.) As it turns out, the current InProcessCompilerDaemonFactory has performance and correctness problems when used with Scala. So once you flip `useAnt` to `false`, it's currently imperative to also flip `fork` to `true`. (`fork` still defaults to `false` to keep backwards compatibility when using the Ant-based compiler.) I also received some feedback from users, which until now didn't bring up any new issues. Cheers, Peter -- View this message in context: http://gradle.1045684.n5.nabble.com/Known-problems-with-new-Scala-features-in-1-3-rc-1-tp5710401.html Sent from the gradle-dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
