Help needed: JetGroovy major change, please help us to test

Hello All,

We've made a major change to JetGroovy to incorporate control-flow-sensitive type inference.

To understand the rationale, please consider the following Groovy code:

def foo = 0 foo = "" foo.toLowerCase() ]]>

In previsous version we failed to understand that in the last statement the actual type is String, so there was no String's completion, nor navigate did work.
The same is true for more complex control flow, e.g. when there are assignments made in different if branches.

This change is rather major, and while all the tests here do pass, there is still a possibility of something being broken, so if you could take the last build from
http://www.jetbrains.net/confluence/display/GRVY/Stable+Versions and use it for some time in your groovy development, we would greatly appreciate your feedback.
This would greatly help us to release the best quality plugin in Autumn.

Thank you in advance,
Eugene.

9 comments
Comment actions Permalink

Eugene,

I'd love to and will, soon.

Would you mind if I post a copy of this message to the Groovy user's mailing list?


Randall Schulz

0
Comment actions Permalink

Hello Randall,

If you're familiar with Groovy (and Groovy-Java interop), could you perhaps
comment on this JIRA ticket?
http://www.jetbrains.net/jira/browse/GRVY-314

-tt


0
Comment actions Permalink

By the way, does this release handle Grails 0.6 (itself currently at RC1)?


RRS

0
Comment actions Permalink

Taras,

I'll look it (the JIRA ticket) over to see if I have anything to contribute, but I'm quite the newbie with Groovy and Grails, so I kind of doubt I'll have anything to say.


Randall Schulz

0
Comment actions Permalink

Hello All,

We've made a major change to JetGroovy to incorporate
control-flow-sensitive type inference.

...

This change is rather major, and while all the tests here do pass,
there is still a possibility of something being broken, so if you could take the last
build from http://www.jetbrains.net/confluence/display/GRVY/Stable+Versions
and use it for some time in your groovy development, we would greatly appreciate your
feedback. This would greatly help us to release the best quality plugin in Autumn.


OK. I've installed it (specifically, version 0.1.10352, according to the plug-in manager).

I immediately find that it's telling me it cannot resolve (Groovy) class names that are in the same directory. This did not happen in the previous version.

On the other hand, in the (statically) scaffolded Grails class that refers to those same class names, no diagnostic results, though those Grails controller classes are not in the same directory as the classes to which they refer.


Randall Schulz

0
Comment actions Permalink

We did not change anything in resolving classes. What you see is probably that the caches format has changed, and we did not update them automatically. Editing the referenced classes should correct the problem.

0
Comment actions Permalink

Hey! How 'bout that.

Red turns to green...


Thanks.

RRS

0
Comment actions Permalink

Is there another way of getting the latest (or latest stable) build other than SVN? I've synched the trunk, but the OpenAPI.jar available with the 7255 build seem to be missing some classes used by the plugin, specifically, XMLElementType,PsiFileImpl and some other classes. Is there a version of OpenAPI in SVN that I can use?

Adam

0
Comment actions Permalink

We use closed api, so you should include idea.jar.

0

Please sign in to leave a comment.