Funnily enough, Scott Hickey, the main guy behind the Eclipse plugin for Grails and Groovy, is the one who worked with me in (a) coming up with the procedure I outlined yesterday and (b) thinking up the possibility of debugging Groovy, in the way demonstrated above! The Grails eXchange is definitely one of the best conferences I have been to, in terms of people freely exchanging ideas and learning from each other's insights and enthusiasms. The main message I'm going home with is the rather obvious realisation that Groovy is in a completely different category to any other scripting language, because of its relationship with Java. Hence, lots of stuff (such as the Java debugger, as indicated above) can simply be reused when working with Groovy. That insight should also inform the tooling provided for Groovy. The closer we stay to Java, the more we can get from it, the less we'll be reinventing the wheel, and the greater the chance that we'll be providing something truly useful for Groovy users in NetBeans IDE.