[GROOVY-9587] Scope of method call changed from non-static to static 2.4->2.5

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.5.12
• Fix Version/s: 4.0.0-alpha-1, 3.0.5, 2.5.13
• Assignee: Eric Milles
• Reporter: Eric Helgeson
• Created: 12/Jun/20 15:26
• Updated: 23/Jul/20 14:16
• Resolved: 15/Jun/20 06:45

Description

 

class Foo { 
   static storageProvider 
   def getStorageProvider(Boolean a) { 
      return storageProvider
   }
   def getStorageProvider() { 
     if(!storageProvider) {
       getStorageProvider(true) // <-- Attempts to call statically in 2.5 
     } 
    return storageProvider
   } 
} 
new Foo().getStorageProvider()

In groovy 2.5+ it seems it gets confused if you have a static variable in a class, say static storageProvider, and a non-static method def getStorageProvider(Boolean x) it tries to call the getStorageProvider(true) statically, which does not exist.

 

In the groovyConsole you can see the change happen between conversion and semantic analysis - it changes from non-static to static.

 

Unsure this is intended or not. I couldn't find mention of it in any changes. It would be nice to document/know why the change happened between 2.4/2.5.