On Wed, Jan 16, 2013 at 2:08 PM, Luke Daley <[email protected]>wrote:
> There was talk around the 1.2 era where we were talking about improving > the user experience when dealing with deprecations. I think we should bump > up the priority of this and address it in the next release or two. > > I just updated an old project to 1.3 and received: “The > Project.dependsOnChildren() method has been deprecated and is scheduled to > be removed in Gradle 2.0.” > > As a user, that's far from helpful. What should I do now? How do I know > what the replacement is? We've already identified things that we could do > to improve this. > > My perception may be off on this in terms of high it is prioritised, but I > feel that it should be higher. It's an easy thing to “forget” about. > This is something we should tackle. We could provide an URL where a user can learn what are the alternatives. Anything else you have in mind to improve this? Hans > > -- > Luke Daley > Principal Engineer, Gradleware > http://gradleware.com > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > >
