HI Matt,

Do you still plan to do this over this weekend?

Thank you,
Gary

On Sun, Jul 16, 2017 at 10:02 AM, Matt Sicker <[email protected]> wrote:

> I found the issues:
>
> https://issues.apache.org/jira/browse/LOG4J2-1431 (for the system
> properties normalization)
> https://issues.apache.org/jira/browse/LOG4J2-1809 (for the supporting API
> addition to log4j-api)
>
> On 14 July 2017 at 15:52, Gary Gregory <[email protected]> wrote:
>
> > On Fri, Jul 14, 2017 at 1:49 PM, Matt Sicker <[email protected]> wrote:
> >
> > > The old names are all translated to normalized names via some magical
> > > regular expressions from what I recall. I should have some time to work
> > on
> > > Log4j stuff this weekend, so I'll try to get that merged as well.
> > >
> >
> > Thank you sir.
> >
> > Gary
> >
> >
> > >
> > > On 14 July 2017 at 15:48, Gary Gregory <[email protected]> wrote:
> > >
> > > > Merge it! :-)
> > > >
> > > > Did you bother to keep the old names for compat?
> > > >
> > > > G
> > > >
> > > > On Fri, Jul 14, 2017 at 1:47 PM, 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]>
> > >
> >
>
>
>
> --
> Matt Sicker <[email protected]>
>

Reply via email to