aheritier olamy Listener logger is existing functionality. I didn't add / change this. Happy to use classical logger technique, was trying to keep the code consistent. It seems a bit odd to me, but I don't have much XP with this plugin so shrugged it off.
Would be for ripping out the current listener logging approach and replacing with just a standard logger approach but I believe that this is out of scope for what this was raised to address.
Happy to raise a separate issue to address the logging implementation and having this depend on it. WDYT?
owood (cc olamy) I don't understand why we don't use classical loggers to record these stacktraces and we are using e.printStackTrace ?!?
owood I'm not sure that only the message may help and we won't need the full stack but we can give it a try (it's cheap)