-
Improvement
-
Resolution: Unresolved
-
Minor
-
None
Definitely not a deal breaker. Just makes debugging hard
catch (InterruptedIOException e) { e.printStackTrace(listener.error("Aborted Maven execution for InterruptedIOException")); return Executor.currentExecutor().abortResult(); }
Propose adding message to printStackTrace. Something like:
catch (InterruptedIOException e) { e.printStackTrace(listener.error("Aborted Maven execution for InterruptedIOException: " + e.getMessage())); return Executor.currentExecutor().abortResult(); }
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)