"a framework in place to migrate property names without disrupting users"?
That is totally new to me. Any pointers?
On Fri, Jan 29, 2021 at 5:01 PM Carter Kozak <cko...@ckozak.net> wrote:
> We have a framework in place to migrate property names without disrupting
> users, I would support using a default name that aligns more closely with
> the feature. I don't think we warn when deprecated names are used, I'd
> expect that could become noisy, and we want folks to upgrade without
> worrying about scaring their users with warnings from us.
>
> For what it's worth, the feature is entirely unnecessary beyond java 8
> since the getName() allocations were removed.
>
> Carter
>
> On Fri, Jan 29, 2021, at 10:53, Volkan Yazıcı wrote:
> > Triggered by Carter's remark... Shall we
> > rename log4j2.asyncLoggerThreadNameStrategy to log4j2.threadNameStrategy
> > and display a warning if the deprecated one is defined? Are there more of
> > such properties?
> >
> > On Fri, Jan 29, 2021 at 4:44 PM Carter Kozak (Jira) <j...@apache.org>
> wrote:
> >
> > > The {{log4j2.asyncLoggerThreadNameStrategy}} may be set to {{UNCACHED}}
> > > to override this default on all systems. It may be set in a
> > > log4j2.component.properties file, or via a jvm system property.
> > > It's a tad odd that these are described as properties for async
> logging,
> > > in reality they're more closely associated with gc-logging, and don't
> > > really relate to asynchronous features. Likely a historical artifact.
> > > Docs:
> > >
> > >
> https://logging.apache.org/log4j/2.x/manual/configuration.html#SystemProperties
> > >
> https://logging.apache.org/log4j/2.x/manual/async.html#SysPropsAllAsync
> > >
> >
>
