For removing Closure, some things we'd need to do: 1. Start documenting these magic methods in the DSL ref somewhere 2. Add support for generating Closure variants for Spec methods
On 26/10/2012, at 10:37 AM, Szczepan Faber wrote: > +1 > > On Wed, Oct 24, 2012 at 10:36 PM, Adam Murdoch > <[email protected]> wrote: >> >> On 25/10/2012, at 12:40 AM, Luke Daley wrote: >> >> As of 1.2, our decorated classes implicitly handle closures for any method >> where Action is the last param. >> >> Do we want to start removing methods that accept Closure as the last param >> from our API? Or should we wait until we have more of an idea how we are >> going to handle these implicit methods WRT IDE support? >> >> >> We should start removing them. We'd deprecate the API method, but not the >> implementation (i.e. no deprecation warning log message). We'd remove the >> API and implementation methods in 2.0. >> >> >> -- >> Adam Murdoch >> Gradle Co-founder >> http://www.gradle.org >> VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting >> http://www.gradleware.com >> > > > > -- > Szczepan Faber > Principal engineer@gradleware > Lead@mockito > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > -- Luke Daley Principal Engineer, Gradleware http://gradleware.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
