Thanks,
I had removed the Groovy plugin from my environment because it was giving me
more pain than help. Since then I have updated Eclipse
from 3.6.2 to 3.7.2 and tried it again. I must say most of the time I simply use println for Groovy debugging (no IDE need). But in
some case the debugger can help indeed.
For your question I guess you are right. It's certainly a side effect of the
refactoring. At least I can't see anything else...
There is currently a mini-language overhaul effort. The screen actions and
minilanguage should have the same behaviour in future,
notably the set action. So hopefully then you should not have to use
GroovyUtil.runScriptAtLocation
Jacques
From: "Leon" <cb.utb...@gmail.com>
hi, Jacqies.
I'm using latest groovy plugin which version is 2.6.1, groovy runtime plugin
1.7.10 and 1.8.6.
--
View this message in context:
http://ofbiz.135035.n4.nabble.com/Unable-to-debug-groovy-script-called-by-screen-widget-tp4533949p4536704.html
Sent from the OFBiz - User mailing list archive at Nabble.com.
