[GRADLE-1875] Cannot use EclipseProject.getGradleProject() or acquire GradleProject model for pre-m5 Gradle versions Created: 27/Oct/11  Updated: 04/Jan/13  Resolved: 27/Mar/12

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: 1.0-rc-1

Type: Bug
Reporter: Adam Murdoch Assignee: Szczepan Faber
Resolution: Fixed Votes: 1


 Description   

EclipseProject.getTasks() is now deprecated, but the replacement EclipseProject.getGradleProject().getTasks() does not work for pre-m5 releases.

 Comments   
Comment by Szczepan Faber [ 13/Mar/12 ]

I'm wondering whether we should care about it... m4 was broken and m3 is veeery old.

Comment by Kris De Volder [ 19/Mar/12 ]

Yes. There are still projects out there that are on M3. (E.g. spring-security).
Perhaps these people can be expected to move on "soon". But the truth is that if there builds are working fine, they may be reluctant to tackle the upgrade.

This problem is quite serious to me now that the method has been removed in M9, I either have these two options:
1) people with M3 projects can no longer run/view any tasks (which also breaks import if those project's import relies on executing some tasks).
2) continue to stick with tooling API M7

So to me that is a real blocker for moving to Tooling API M9.

For now I'm going with (2). But if EclipseProject.getEclipseTasks is put back in some snapshot build. I may consider basing the next STS-Gradle support of off that Gradle snapshot build instead.

Kris

Comment by Kris De Volder [ 20/Mar/12 ]

Please raise this issue to 'Critical' or 'Blocker'. This is a blocker. The tooling M9 API is unusable for me. I.e. I can not consider upgrading STS to use M9 until the EclipseProject.getTasks method is put back in.

Comment by Adam Murdoch [ 20/Mar/12 ]

@Kris, this should be fixed soon.

Comment by Kris De Volder [ 23/Mar/12 ]

This isues blocks: https://issuetracker.springsource.com/browse/STS-2509

Comment by Kris De Volder [ 23/Mar/12 ]

Also blocking: https://issuetracker.springsource.com/browse/STS-2276

Comment by Kris De Volder [ 23/Mar/12 ]

Also blocking: https://issuetracker.springsource.com/browse/STS-2503

Comment by Kris De Volder [ 23/Mar/12 ]

Also blocking: https://issuetracker.springsource.com/browse/STS-2213

Comment by Kris De Volder [ 23/Mar/12 ]

And this one too: https://issuetracker.springsource.com/browse/STS-2456

Comment by Szczepan Faber [ 27/Mar/12 ]

It's fixed now. You can do EclipseProject.getGradleProject().getTasks() also from M3+ target gradle version.

Comment by Kris De Volder [ 27/Mar/12 ]

Excellent! Thanks for that.
Do you recommend a particular Gradle snapshot build for me to use, or should I just pick whatever is the latest at the moment?

Kris

Comment by Szczepan Faber [ 27/Mar/12 ]

Let me kick off a nightly build and get back once it's ready

Comment by Szczepan Faber [ 27/Mar/12 ]

Can you try nightly: http://gradle.org/nightly ?

Comment by Szczepan Faber [ 27/Mar/12 ]

Can you try nightly: http://gradle.org/nightly ?

Comment by Kris De Volder [ 02/Apr/12 ]

FYI: I've succesfully updated STS Gradle tools to use an RC1 buildsnapshot of the tooling API. All of my regression tests are green. Using EclipseProject.getGradleProject().getTasks() instead of the deprecated method it replaces.

Comment by Szczepan Faber [ 02/Apr/12 ]

Awesome, thanks for feedback.

Generated at Wed Jun 30 12:06:43 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.