By the way, if you were suggesting to rename the branch to release-3.x for symmetry or anything, that’d be fine. I mostly meant we don’t need a third main branch.
On Wed, Jun 17, 2020 at 04:20 Volkan Yazıcı <[email protected]> wrote: > Not really, since > > 1. I cannot do anything for YAML and XML layouts, obviously. > > 2. JsonLayout can leverage JsonTemplateLayout with the > exception of stack traces, since Jackson serializes `Throwable`s > "as is" with nested `StackTraceElement`s, which is, IMHO, > pretty unconventional and I prefer not to implement this feature > in JTL. > > On Mon, Jun 15, 2020 at 11:49 PM Ralph Goers <[email protected]> > wrote: > > > > Is it possible to modify those Layouts to use yours instead? I’d prefer > not to break existing applications. > > > > Ralph > > > > > On Jun 15, 2020, at 11:36 AM, Volkan Yazıcı <[email protected]> > wrote: > > > > > > Hello, > > > > > > I want to go forward and delete log4j-layout-jackson-* modules from > > > the master. This will effectively remove JsonLayout, XmlLayout, and > > > YamlLayout. Given these changes break backward compatibility, shall I > > > introduce these changes to a new release-3.x branch? Maybe this is a > > > good moment to discuss how we think about maintaining these modules in > > > the future. > > > > > > For the records, I think Jackson serialized LogEvent layouts are not > > > really practical due to a severe behaviour: stack traces are > > > serialized as nested documents. Eventually these layouts need to be > > > persisted somewhere and none of the document stores that I know of > > > support such deeply nested schemas. > > > > > > Kind regards. > > > > > > > > -- Matt Sicker <[email protected]>
