I’ve opened https://github.com/apache/logging-log4j2/pull/1199 to handle this
issue. The vast majority of the changes are from replacing `Layout`. Please take a look and provide any
feedback.
+1
Thanks for working on this! Looks great!
> On Jan 10, 2023, at 4:55 AM, Volkan Yazıcı wrote:
>
> The Apache Log4j Tools 0.1.0 release is now available for voting.
>
> The 0.1.0 version is the very first release of this relatively old
> repository, which is repurposed for `log4j-changelog`,
On Fri, Jan 06, 2023 at 08:40:57PM -0500, Robert Middleton wrote:
> The release has been formally completed at this point; mirrors have
> their copy of the official tar.gz file.
log4xx 1.0.0 just migrated to Debian/testing, so the transistio is done :)
--
tobi
> -Robert Middleton
>
> On Fri, J
Is the generic needed at all?
Gary
On Wed, Jan 11, 2023, 12:19 Matt Sicker wrote:
> I’ve opened https://github.com/apache/logging-log4j2/pull/1199 to handle
> this issue. The vast majority of the changes are from replacing `Layout extends Serializable` with just `Layout`. Please take a look and
+1
On Thu, Jan 12, 2023 at 2:21 AM Matt Sicker
wrote:
> +1
>
> Thanks for working on this! Looks great!
>
> > On Jan 10, 2023, at 4:55 AM, Volkan Yazıcı wrote:
> >
> > The Apache Log4j Tools 0.1.0 release is now available for voting.
> >
> > The 0.1.0 version is the very first release of this r
Not really I guess? Layout already extends Encoder, and the only
reasonable return value now is String since byte[] is already covered by
another method, and ByteBuffer is covered by the Encoder interface. That could
further simplify things!
—
Matt Sicker
> On Jan 11, 2023, at 14:50, Gary Grego
