I tend to agree with you but it does get a little tricky. If "my own
user code" is making use of e.g. Java collection classes, then
sometimes I'd really like to see "one level down".
Take this example:
///
def list = [null, 'a', 'b', 'c', 'd', 'e', 'f']
assert
On 23.06.22 11:41, Paul King wrote:
I tend to agree with you but it does get a little tricky. If "my own
user code" is making use of e.g. Java collection classes, then
sometimes I'd really like to see "one level down".
one level down... well, for you in
[...]
Caught: java.lang.NullPointerExce
Hi there,
not sure if it helps, but myself, I've played with the sanitizer, and
eventually wrote my own track dumper which does two parts:
- first, it dumps my own code only (plus some extras, e.g., for internally
compiled scripts it shows the offending line, etc.)
- after that, it dumps full st
Groovy-Eclipse uses this list to "shade" (not remove) stack trace elements:
com.sun
groovy.lang
groovyjarjarasm
java.lang.reflect
jdk.internal
org.apache.groovy
org.codehaus.groovy
sun
I add java.util.stream in my workspace for the internal iteration of collect,
etc.
Also lambdas tend to creat
Okay, I added a comment in the existing issue[1] indicating that we
will likely pursue the idea of a list of "soft" package/class prefixes
before removing "java." (and maybe "groovy.") from the current
sanitization list. Where the exact details of "soft" are still to be
worked out.
I created anoth
