On 14/11/2012, at 2:30 PM, Peter Niederwieser wrote: > 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.
Can we live with these issues for 1.3? I'd rather just have a shorter 1.4 cycle than another 1.3 release candidate cycle, but if we need to we can do an rc2. -- Adam Murdoch Gradle Co-founder http://www.gradle.org VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting http://www.gradleware.com
