commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Gregory <garydgreg...@gmail.com>
Subject Re: [JCS] update to Log4j 2 facade API
Date Tue, 05 Sep 2017 18:13:06 GMT
On Tue, Sep 5, 2017 at 11:03 AM, Ralph Goers <ralph.goers@dslextreme.com>
wrote:

>
> > On Sep 5, 2017, at 9:19 AM, Romain Manni-Bucau <rmannibucau@gmail.com>
> wrote:
> >
> > Le 5 sept. 2017 17:35, "Ralph Goers" <ralph.goers@dslextreme.com
> <mailto:ralph.goers@dslextreme.com>> a écrit :
> >
> >
> >> On Sep 5, 2017, at 6:45 AM, Romain Manni-Bucau <rmannibucau@gmail.com>
> > wrote:
> >>
> >>>
> >>
> >> I think it must go the other way: log4j2 must push projects to move
> >> otherwise projects will be happy with X -> log4j2 bridges, no?
> >
> > We already have support for bridging other APIs to Log4j 2.
> >
> >
> > Not bypassing jul impl without a logmanager right? That is what does
> > frameworks api
>
> Is what you are asking for the same as what is asked for in
> https://issues.apache.org/jira/browse/LOG4J2-2025? <
> https://issues.apache.org/jira/browse/LOG4J2-2025?> If so, I am planning
> on doing that although that integration will not make users very happy.
> This is one of the reasons that jul sucks.
>

Ralph,

Do you want to assign that issue to yourself? That would allow others to
focus on different tickets.

Gary


>
> Ralph

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message