Github user bsokolovu commented on the issue:
https://github.com/apache/logging-log4j2/pull/78
Hi gatekeepers!
Are you going to merge it and use it? Or you have new comments? Or you just
forgot about it? ))
---
If your project is set up for it, you can reply to this email and
Github user bsokolovu commented on the issue:
https://github.com/apache/logging-log4j2/pull/78
I've amended commit with unit test.
And once more about serialVersionUID - it's not a new version of entity.
It's fix for serialization of an old version. If you revert
Github user bsokolovu commented on the issue:
https://github.com/apache/logging-log4j2/pull/78
I don't see reasons to change serialVersionUID. It's not new version of
entity.
I'd like to add unit test but I can't build even `master` branch because of
some od
GitHub user bsokolovu opened a pull request:
https://github.com/apache/logging-log4j2/pull/78
Fix writeObject in FormattedMessage.
To pass `FormattedMessage` completely we should pass string values from
`argArray` together with `argArray.length`.
For now there is such bug: on
