Adam Murdoch wrote > 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.
They aren't blockers, but it would nice to have them fixed in 1.3 final (especially the verbose logging). In any case, how are we going to solve 2.? From my experience, in-process compilation leads to the build daemon running out of permgen quickly (after just a few builds). So one solution is to change the default for `fork` to `true` (affecting both Ant-based and Zinc-based compiler) and to simply disallow the combination fork=false, useAnt=false. In other words, I wonder if there is a point in trying to get InProcessCompilerDaemonFactory to work with Scala. Thoughts? Cheers, Peter -- View this message in context: http://gradle.1045684.n5.nabble.com/Known-problems-with-new-Scala-features-in-1-3-rc-1-tp5710401p5710406.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
