You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by GitBox <gi...@apache.org> on 2020/02/06 08:43:24 UTC

[GitHub] [maven-surefire] ajohnstonTE commented on issue #269: [SUREFIRE-1748] Fix reporting of empty stack trace messages

ajohnstonTE commented on issue #269: [SUREFIRE-1748] Fix reporting of empty stack trace messages
URL: https://github.com/apache/maven-surefire/pull/269#issuecomment-582795866
 
 
   Sure, I'll help out on that. If I understand you correctly, the change would be: 
   
   Rather than encoding the events as values separated by colons, with there being an expected number of values in expected positions for the different event types, it would instead serialize the events into JSON. That JSON would get serialized into base64, then consumed on the other end and deserialized back into JSON, and finally deserialized back into the original event classes. That sound right?

----------------------------------------------------------------
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