Unexpected runtime error while computing a text hover

On attached screenshot the error always occurs when hovering on $

I can't see in the screenshot, but what is the type of the field you are hovering over?

The error occurs in groovy class DrupalGitProject. infoFile is an instance variable declared in the groovy superclass DrupalProject. It's type is DrupalInfoFile, a groovy class in the same package which has nothing much in itself:

class DrupalGitProject extends DrupalProject {
...
abstract class DrupalProject extends EclipseIProject {
public static final java.lang.String STANDALONE = 'standalone'
DrupalComponent drupalComponent
String rootProjectName
DrupalInfoFile infoFile
...
class DrupalInfoFile {
public static final String PHP_INI_OPTION_PATTERN = /\s*(\w+)([\w*])\s=\s*(.*)/
public static final String COMMENT = '; Values below added by Groovy Drupal'
File file = null
...

I am not able to reproduce this given the information you have currently provided. Can you send me over a copy of the project to my personal email?

It looks to me like the CodeSelect engine (ie- the thing that produces hovers) thinks that infoFile is a method, and so it is failing to produce a correct method signature for the text in the hover.

Thanks for the test project. I see what is happening now. Groovy-Eclipse is getting confused because there is a field named infoFile and there is also a method named getInfoFile. The inferencing engine wants to choose the getter instead of the actual field. In most cases, this works fine. If you try to navigate (F3), then you are taken to the getter method instead of the field. However, when hovering this breaks since the hover engine is expecting a field, but is passed a method instead.

I'm a little surprised that this hasn't come up earlier since this seems like a fairly typical use case to explicitly override a property with a getter.

I'll experiment a bit more before deciding on the best way to fix.

Now, the interesting is that when I naively try to recreate this in a simpler project, there is no problem.

All issues resolved. Committed with regression tests.

Now, code select will try first to match against a method of the exact name, then a field of the exact name. Finally, if neither matches, then getter and setter variants of the name will be tried. This will make the hovers more like what you would expect and there should be no more exceptions when hovering.