Was wondering what you found out... I have a lot of places now where it would be much better if I could break up my classes for better reusability but can't because of this issue. Also, since my classes have to contain all the code, the classes are getting pretty big... again, I could make the code a lot better if I could appropriately break out common methods.
Note: I've also tried to extend a groovy "superclass" as well create a class method (vs. an instantiated method) to try to work around this issue but also get the same error (can't resolve class) so it APPEARS to be the same issue or related to it.
Have you been able to reproduce and/or has it been fixed?
Thanks!
Jim
