maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <...@apache.org>
Subject [GitHub] [maven-surefire] ajohnstonTE commented on issue #269: [SUREFIRE-1748] Fix reporting of empty stack trace messages
Date Sat, 08 Feb 2020 05:31:48 GMT
ajohnstonTE commented on issue #269: [SUREFIRE-1748] Fix reporting of empty stack trace messages
URL: https://github.com/apache/maven-surefire/pull/269#issuecomment-583705042
 
 
   Does the transport layer need to change? Or more specifically, in what way would we change
it? From what I can tell, the existing functionality simply captures the stderr/out of the
forked process.
   
   I think I understand the lack of need for Base64, but only insofar as avoiding collisions
with `:`. I don't actually know what the issue would have been before with non-ASCII encodings.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

Mime
View raw message