Said branch continues to support the alternate naming schemes as fallbacks, but it prioritizes the log4j2.* naming scheme.
On 14 July 2017 at 15:47, Matt Sicker <[email protected]> wrote: > I have an open branch that fixes all this. The only remaining work there > is to clean up merge conflicts and update the documentation to use log4j2.* > everywhere. > > On 14 July 2017 at 15:46, Gary Gregory <[email protected]> wrote: > >> Hi All, >> >> Our sys prop naming is driving me nuts! >> >> Sometimes it's "log4j.foo", sometimes it's "log4j*2*.bar", sometimes its >> "bar". WTF! >> >> Can we just PLEASE bite the bullet and make it all "log4j2." or >> _something_ >> >> We could keep the existing names for compat (TDB). >> >> ? >> >> Gary >> > > > > -- > Matt Sicker <[email protected]> > -- Matt Sicker <[email protected]>
