[GROOVY-2032] MetaClassImpl invokeStaticMethod recurses up the class hierarchy losing the original sender

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.0, 1.1-beta-1, 1.1-beta-2
• Fix Version/s: 1.1-beta-3
• Assignee: Graeme Rocher
• Reporter: Graeme Rocher
• Created: 09/Aug/07 08:00
• Updated: 09/Aug/07 08:06
• Resolved: 09/Aug/07 08:05

Description

Currently if you do

class A {}
class B extends A{}

Boo.foo()

You get:
groovy.lang.MissingMethodException: No signature of method: static A.foo() is applicable for argument types: () values: {}

This is because invokeStaticMethod uses recursion up the class hierarchy and loses the original sender information. This makes for bad error messages and also result in other problems such as if B defines a "methodMissing" it is never invoked.