On 14/11/2012, at 6:51 AM, Peter Niederwieser wrote: > 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).
Absolutely. There was an implicit gap between switching the default and deprecating the ant based implementation, just like we did for the Java and Groovy compilers. So, in the 1.4/1.5 timeframe we'd switch the defaults, and maybe 3 or 4 releases after that think about deprecating the Ant based implementation. > Until Zinc has proven to be mature (e.g. regarding backward > compatibility) and provides a way to do non-incremental compilation, Why would you want to do non-incremental compilation? Just curious. -- Adam Murdoch Gradle Co-founder http://www.gradle.org VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting http://www.gradleware.com
