Adam Murdoch wrote > On 14/11/2012, at 1:10 AM, Peter Niederwieser wrote: > >> Which release(s) should we target for these features? > > Not sure yet. Probably not 1.4.
I'd like to add that I consider the REPL story the most important. Handling console input/output well is not just important for the Scala REPL, but for Gradle in general. At the very least, this means to have a way to eliminate the Gradle status line. From what I can tell, this would already give a usable REPL, if not in all its glory. Adam Murdoch wrote > Can you add these to the scala spec, just as notes about future things we > can do? Will do so. Adam Murdoch wrote >> Anything important I missed? > > * Make the zinc based compiler implementation the default and deprecate > the ant task based implementation. This is a candidate for 1.4. I wouldn't feel comfortable with this at this point (especially the deprecation). Until Zinc has proven to be mature (e.g. regarding backward compatibility) and provides a way to do non-incremental compilation, I think there are valid reasons for wanting to use the Ant-based compiler (e.g. for CI/release builds, or for Scala versions that Zinc cannot (yet) handle, or for Scala versions that only a new Zinc version can handle that's not backward compatible with the Zinc version that we compile against). I do second the longer term goal of getting rid of the Ant based compiler. To that end, I've made a feature request to have a unified Scala compiler API for incremental and non-incremental compilation. Cheers, Peter -- View this message in context: http://gradle.1045684.n5.nabble.com/Next-steps-in-improving-our-Scala-support-tp5710388p5710395.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
