This is a tough one: Developing the IDE Support to debug the execution of Groovy Sourcode.
I can imagine that this is very difficult and time consuming.
However I think it is a key feature to develop complex applications.
Wouldn't it make sense to work on this with higher priority?
I agree. Increasing priority. On the other hand there is always a high level plan at the beginning of the release where
IZ priority is not the only criteria. In this terms this definitely has a high priority.
BTW You can debug grails app even these days (although not directly supported):
1) run grails-debug run-app from command line
2) choose Debug/Attach Debugger
3) configure you breakpoints
4) inspect local variables (groovy expressions not yet supported)
Attaching the patch - to be applied post 6.8 (GroovyEvaluator is just placeholder now). Feel free to test.
Created attachment 90085 [details]
*** Issue 162865 has been marked as a duplicate of this issue. ***
*** Issue 166830 has been marked as a duplicate of this issue. ***
Fixed in web-main f889ef0057dd.
The target milestone is 6.9? Is this going to be in 6.8 now?
No. It is going to be in dev build (trunk) and 6.9. There is a chance for this being in 6.8.1.
We are in feature freeze period for some time (see comment #3).
Integrated into 'main-golden', will be available in build *200912010200* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Log: #123169 groovy debugging support
*** Bug 179807 has been marked as a duplicate of this bug. ***