This forum is now a read-only archive. All commenting, posting, registration services have been turned off. Those needing community support and/or wanting to ask questions should refer to the Tag/Forum map, and to http://spring.io/questions for a curated list of stackoverflow tags that Pivotal engineers, and the community, monitor.

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 Attachment ).
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).

Comment

Hi Andy,
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.

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.

Cheers
Davide

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).

Comment

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