On 13/11/2012, at 2:10 PM, Peter Niederwieser wrote: > Now that 1.3 is almost out, I'd like to discuss potential next steps for > improving our Scala support. Here is an initial list: > > * Scala REPL support > To make this work well, we need to solve the general problem of Java code > reading from and writing to the console when running in Gradle (with and > without Gradle Daemon). Currently, there are issues with the Gradle status > line getting in the way, and control characters not being interpreted > correctly. The latter is important for accessing the shell's history. > > * Reusing the Scala compiler across builds > We already reuse the compiler across ScalaCompile tasks in the same > build, which led to big performance improvements. Reusing the compiler > across builds (as done by sbt and Zinc/Nailgun) will provide further gains. > In other words, we need to enhance the compiler daemon so that it can > outlive a build. Question is if we add this capability specifically for the > compiler daemon, or work towards a unified solution (for all daemons, or for > all daemons except the Gradle Daemon).
Without knowing the technical details, it seems crazy to me to do a Scala specific solution here. > * First class support for ScalaTest and Specs2 > Investigate if the JUnit runners are good enough, or if direct support is > desirable. > > Which release(s) should we target for these features? Anything important I > missed? -- Luke Daley Principal Engineer, Gradleware http://gradleware.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
