d) It wasn't supposed to be removed (it wasn't on the list), but seems to have gone anyway. We'll either put it back or fix EclipseProject.getGradleProject().getTasks().
Cool. FYI: I would prefer the latter. If I know that EclipseProject.getGradleProject().getTasks() works for M3 and above I'd switch to using that. Otherwise I will be forced to continue using deprecated EclipseProject.getTasks. However if making getGradleProject work for pre M5 is really hard... then putting EclipseProject.getTasks back for now would certainly be fine. I just found this Jira issue as well http://issues.gradle.org/browse/GRADLE-1875 So it looks like the significance of removing it was known. I'll put further comments there. Kris ----- Original Message ----- > On 20/03/2012, at 6:44 AM, Kris De Volder wrote: > > It looks like the M9 tooling API has removed deprecated method > > EclipseProject.getTasks. > > > I recall that previously deprecation comment advised me that I > > should > > instead do something like > > > eclipseProject.getGradleProject().getTasks() > > > The problem with that however is that this sequence of method calls > > isn't working for older projects (e.g. M3 based projects). > > > (getProject method throws MissingMethodException). > > > So does this effectively mean that > > > a) M9 tooling API is not intending to support working with M3(*) > > based projects? > > > b) The deprecated method was removed from tooling API without > > considering this unintended consequence? > > > c) there is another method in M9 that works with M3 to get tasks > > for > > a given EclipseProject that I have overlooked? > > d) It wasn't supposed to be removed (it wasn't on the list), but > seems to have gone anyway. We'll either put it back or fix > EclipseProject.getGradleProject().getTasks(). > -- > Adam Murdoch > Gradle Co-founder > http://www.gradle.org > VP of Engineering, Gradleware Inc. - Gradle Training, Support, > Consulting > http://www.gradleware.com
