Jun 21st, 2011, 10:05 AM
Getting senseless errors on groovy editor such "Groovy:unable to resolve class E"
Hi, we occasionally obtain unreasonable errors for groovy source:
- Groovy:unable to resolve class E
- The type Object is not generic; it cannot be parameterized with arguments <E>
They mostly occur in pair and for sources that has no real errors (see a screenshot at groovyerror.jpg).
When this starts to happen, it propagates to many groovy files, and to remove that noisy fake errors we have to edit every class adding a type to make it generic, save, then remove the changes and save another time.
Any idea? Could it be somewhat related to groovy joint-compilation? (This is a project that mixes java and groovy sources).
We are using STS 2.7.0.M2, and I suspect it started to happen after upgrade to M2 (but I'm not really sure).
Jun 21st, 2011, 10:25 AM
This was fixed in the last few days, please upgrade to a recent groovy-eclipse dev build using the update site:
Jun 22nd, 2011, 01:41 AM
it's very strange: I always had that update site (enabled) and I don't have proposal for updates (I'd expect to have a new version every night more or less). I installed Groovy support from STS extensions.
So I have this version of
Groovy version: org.codehaus.groovy
If I search groovy from all available software sites I see this is the installed version
Groovy-Eclipse Feature 2.1.3.xx-20110426-1500-e36 (it comes from http://dist.springsource.com/milesto...vy-grails/e3.6)
but if I specifically choose http://dist.codehaus.org/groovy/dist...snapshot/e3.6/ I can see
Groovy-Eclipse Feature 2.5.1.xx-20110620-2000-e36
Maybe I never had proposed updates from the snapshot update site cause I didn't install groovy from there.
So now I'm going to install the latter (hope it overrides the one installed from groovy-grails update site...). I'm afraid keeping a clean installation of eclipse-based IDE is not as easy as it should be.
PS: Another strange thing: the groovy-eclipse plugin is not visible on the intallation history tab. I'd like to take a look at when I intalled that version, since I don't remember having accepted that update (I could be wrong).
Originally Posted by Andy Clement
Last edited by d_cavestro; Jun 22nd, 2011 at 01:45 AM.
Jun 22nd, 2011, 09:18 AM
I am also seeing a lot of these "Groovy:unable to resolve class ..." in unreasonable locations.
I have Groovy-Eclipse Feature 2.5.1.xx-20110620-2000-e36 installed from the snapshot update site, the behavior started after I upgraded to 2.5.1.xx-20110620-2000-e36