On 14.11.19 17:47, Kerridge, Jon wrote: [...]
It would appear that Intellij invokes the RootLoader in some way when you invoke these processes from within the IDE.
[...]
I now have to find a way of stopping Intellij from loading the RootLoader but that is altogether a different problem and nothing to do with Groovy.
I think I recall that is how they execute Groovy files... if you had a file with a main method, that starts the scripts you would not have this problem. I for example had for Groovy testing always a setup with main class groovy.ui.GroovyMain, program arguments test.groovy, working directory ~/coding/scripts And an appropriately defined classpath. This was then using ~/coding/scripts/test.groovy as the entry script to be executed and picking up all the other scripts relative to this path according to their package definitions.... which means same directory if there are none. There you have no pain with RootLoader. (GroovyMain is in the our jar)
My apologies for having asked an inappropriate question of fellow Groovy developers
Nothing inappropriate here, don't worry. bye Jochen