ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gintautas Grigelionis <>
Subject Bz 62324
Date Fri, 08 Jun 2018 19:08:57 GMT
I was advised to solicit opinions regarding the change introduced as a fix
for the abovementioned issue. It concerns how an event that has both a
message and an exception is logged.

Namely, a stack trace of the exception is logged (in debug mode only)
without any separator from the preceding message. While it seems that the
idea is that the stack trace should be presented as a continuation of the
message, IMO it would require a specially formatted message or, well, some
separator to be visually consistent.

So the question is whether there is better solution than the one currently


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message