Re: [contribution] a Logback integration with OSGi Log 1.4

[Raymond Auge]

@Karl, regarding the vote! I'm ready if you are. :)

- Ray

On Tue, Apr 17, 2018 at 11:01 AM, Raymond Auge 
wrote:

> You're right Simon. Fixed!
>
> I was using this mostly with Equinox on the framework classpath (via it's
> embedded Eclipse Hook).
>
> But I fixed it because I do want this to work in any framework with any
> 1.4 Log impl.
>
> Hopefully when felix gets a 1.4 Log impl, we can do the same early binding.
>
> - Ray
>
>
> On Tue, Apr 17, 2018 at 7:44 AM, Simon Chemouil 
> wrote:
>
>> Ray,
>>
>> Great!
>>
>> It seems this bundle has to be started before the OSGi LogService
>> implementation bundle? I'd expect the Activator to use a service tracker?
>>
>> Simon
>>
>> Raymond Auge a écrit le 12/04/2018 à 16:44 :
>> > As promised here's the repo https://github.com/rotty3000/o
>> sgi.to.logback
>> >
>> > - Ray
>> >
>> > On Thu, Apr 12, 2018 at 7:23 AM, Simon Chemouil 
>> wrote:
>> >
>> >> Hi,
>> >>
>> >> This sounds great. I'd probably use it! I usually use logback with
>> >> static loggers but I might migrate (back) to OSGi Log 1.4 and that
>> seems
>> >> like a nice way to do this smoothly.
>> >>
>> >> Simon
>> >>
>> >>
>> >> Raymond Auge a écrit le 11/04/2018 à 19:08 :
>> >>> Hello everyone,
>> >>>
>> >>> I'm wondering if there would be interest in the felix project to
>> accept
>> >> and
>> >>> host a small integration between the upcoming Log 1.4 specification
>> with
>> >>> Logback backend.
>> >>>
>> >>> The features I have already are:
>> >>>
>> >>> - single bundle impl
>> >>> - generic LogListener that attempts to be the shortest path from the
>> log
>> >>> record (LogEntry) creation to the Logback appenders (no
>> intermediaries)
>> >>> - fully integrates all the record details like location, stackframes,
>> >> etc.
>> >>> - allows Logback to manage levels for legacy framework, service and
>> >> bundle
>> >>> events in a granular fashion by using canonical logger names
>> >>> - can react to Logback scan (i.e. autoupdate) to dynamically apply
>> level
>> >>> changes using the new LoggingAdmin
>> >>> - fully supports all other logback configuration goodness
>> >>> - makes it very simply pipe all the various Log APIs to the same
>> >> appenders
>> >>> (or not) using the same formats (or not) and control all their log
>> levels
>> >>> in one place: slf4j is native, but I've tested with log4j 1.2/2.x,
>> >>> commons-logging, JUL, jboss-logging in the same framework
>> >>>
>> >>> Of course Felix doesn't have a Log 1.4 impl yet so that is a
>> >> consideration.
>> >>>
>> >>> This small integration has solved so many of the rather bothersome
>> >> logging
>> >>> issues I've been suffering the past years and I'd like to share it
>> with
>> >>> others.
>> >>>
>> >>> Sincerely,
>> >>>
>> >>
>> >>
>> >
>> >
>>
>>
>
>
> --
> *Raymond Augé* 
>  (@rotty3000)
> Senior Software Architect *Liferay, Inc.* 
>  (@Liferay)
> Board Member & EEG Co-Chair, OSGi Alliance 
> (@OSGiAlliance)
>



-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)
Board Member & EEG Co-Chair, OSGi Alliance  (@OSGiAlliance)

Re: [contribution] a Logback integration with OSGi Log 1.4

[Raymond Auge]

You're right Simon. Fixed!

I was using this mostly with Equinox on the framework classpath (via it's
embedded Eclipse Hook).

But I fixed it because I do want this to work in any framework with any 1.4
Log impl.

Hopefully when felix gets a 1.4 Log impl, we can do the same early binding.

- Ray


On Tue, Apr 17, 2018 at 7:44 AM, Simon Chemouil  wrote:

> Ray,
>
> Great!
>
> It seems this bundle has to be started before the OSGi LogService
> implementation bundle? I'd expect the Activator to use a service tracker?
>
> Simon
>
> Raymond Auge a écrit le 12/04/2018 à 16:44 :
> > As promised here's the repo https://github.com/rotty3000/osgi.to.logback
> >
> > - Ray
> >
> > On Thu, Apr 12, 2018 at 7:23 AM, Simon Chemouil 
> wrote:
> >
> >> Hi,
> >>
> >> This sounds great. I'd probably use it! I usually use logback with
> >> static loggers but I might migrate (back) to OSGi Log 1.4 and that seems
> >> like a nice way to do this smoothly.
> >>
> >> Simon
> >>
> >>
> >> Raymond Auge a écrit le 11/04/2018 à 19:08 :
> >>> Hello everyone,
> >>>
> >>> I'm wondering if there would be interest in the felix project to accept
> >> and
> >>> host a small integration between the upcoming Log 1.4 specification
> with
> >>> Logback backend.
> >>>
> >>> The features I have already are:
> >>>
> >>> - single bundle impl
> >>> - generic LogListener that attempts to be the shortest path from the
> log
> >>> record (LogEntry) creation to the Logback appenders (no intermediaries)
> >>> - fully integrates all the record details like location, stackframes,
> >> etc.
> >>> - allows Logback to manage levels for legacy framework, service and
> >> bundle
> >>> events in a granular fashion by using canonical logger names
> >>> - can react to Logback scan (i.e. autoupdate) to dynamically apply
> level
> >>> changes using the new LoggingAdmin
> >>> - fully supports all other logback configuration goodness
> >>> - makes it very simply pipe all the various Log APIs to the same
> >> appenders
> >>> (or not) using the same formats (or not) and control all their log
> levels
> >>> in one place: slf4j is native, but I've tested with log4j 1.2/2.x,
> >>> commons-logging, JUL, jboss-logging in the same framework
> >>>
> >>> Of course Felix doesn't have a Log 1.4 impl yet so that is a
> >> consideration.
> >>>
> >>> This small integration has solved so many of the rather bothersome
> >> logging
> >>> issues I've been suffering the past years and I'd like to share it with
> >>> others.
> >>>
> >>> Sincerely,
> >>>
> >>
> >>
> >
> >
>
>


-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)
Board Member & EEG Co-Chair, OSGi Alliance  (@OSGiAlliance)

Re: [contribution] a Logback integration with OSGi Log 1.4

[Simon Chemouil]

Ray,

Great!

It seems this bundle has to be started before the OSGi LogService
implementation bundle? I'd expect the Activator to use a service tracker?

Simon

Raymond Auge a écrit le 12/04/2018 à 16:44 :
> As promised here's the repo https://github.com/rotty3000/osgi.to.logback
> 
> - Ray
> 
> On Thu, Apr 12, 2018 at 7:23 AM, Simon Chemouil  wrote:
> 
>> Hi,
>>
>> This sounds great. I'd probably use it! I usually use logback with
>> static loggers but I might migrate (back) to OSGi Log 1.4 and that seems
>> like a nice way to do this smoothly.
>>
>> Simon
>>
>>
>> Raymond Auge a écrit le 11/04/2018 à 19:08 :
>>> Hello everyone,
>>>
>>> I'm wondering if there would be interest in the felix project to accept
>> and
>>> host a small integration between the upcoming Log 1.4 specification with
>>> Logback backend.
>>>
>>> The features I have already are:
>>>
>>> - single bundle impl
>>> - generic LogListener that attempts to be the shortest path from the log
>>> record (LogEntry) creation to the Logback appenders (no intermediaries)
>>> - fully integrates all the record details like location, stackframes,
>> etc.
>>> - allows Logback to manage levels for legacy framework, service and
>> bundle
>>> events in a granular fashion by using canonical logger names
>>> - can react to Logback scan (i.e. autoupdate) to dynamically apply level
>>> changes using the new LoggingAdmin
>>> - fully supports all other logback configuration goodness
>>> - makes it very simply pipe all the various Log APIs to the same
>> appenders
>>> (or not) using the same formats (or not) and control all their log levels
>>> in one place: slf4j is native, but I've tested with log4j 1.2/2.x,
>>> commons-logging, JUL, jboss-logging in the same framework
>>>
>>> Of course Felix doesn't have a Log 1.4 impl yet so that is a
>> consideration.
>>>
>>> This small integration has solved so many of the rather bothersome
>> logging
>>> issues I've been suffering the past years and I'd like to share it with
>>> others.
>>>
>>> Sincerely,
>>>
>>
>>
> 
> 

Re: [contribution] a Logback integration with OSGi Log 1.4

[Karl Pauls]

Hi Ray,

looks good to me. As there doesn't seem to be any concerns I would
like to get this to a vote. Do you want me to call it or do you want
to do that yourself?

regards,

Karl

On Thu, Apr 12, 2018 at 4:44 PM, Raymond Auge  wrote:
> As promised here's the repo https://github.com/rotty3000/osgi.to.logback
>
> - Ray
>
> On Thu, Apr 12, 2018 at 7:23 AM, Simon Chemouil  wrote:
>
>> Hi,
>>
>> This sounds great. I'd probably use it! I usually use logback with
>> static loggers but I might migrate (back) to OSGi Log 1.4 and that seems
>> like a nice way to do this smoothly.
>>
>> Simon
>>
>>
>> Raymond Auge a écrit le 11/04/2018 à 19:08 :
>> > Hello everyone,
>> >
>> > I'm wondering if there would be interest in the felix project to accept
>> and
>> > host a small integration between the upcoming Log 1.4 specification with
>> > Logback backend.
>> >
>> > The features I have already are:
>> >
>> > - single bundle impl
>> > - generic LogListener that attempts to be the shortest path from the log
>> > record (LogEntry) creation to the Logback appenders (no intermediaries)
>> > - fully integrates all the record details like location, stackframes,
>> etc.
>> > - allows Logback to manage levels for legacy framework, service and
>> bundle
>> > events in a granular fashion by using canonical logger names
>> > - can react to Logback scan (i.e. autoupdate) to dynamically apply level
>> > changes using the new LoggingAdmin
>> > - fully supports all other logback configuration goodness
>> > - makes it very simply pipe all the various Log APIs to the same
>> appenders
>> > (or not) using the same formats (or not) and control all their log levels
>> > in one place: slf4j is native, but I've tested with log4j 1.2/2.x,
>> > commons-logging, JUL, jboss-logging in the same framework
>> >
>> > Of course Felix doesn't have a Log 1.4 impl yet so that is a
>> consideration.
>> >
>> > This small integration has solved so many of the rather bothersome
>> logging
>> > issues I've been suffering the past years and I'd like to share it with
>> > others.
>> >
>> > Sincerely,
>> >
>>
>>
>
>
> --
> *Raymond Augé* 
>  (@rotty3000)
> Senior Software Architect *Liferay, Inc.* 
>  (@Liferay)
> Board Member & EEG Co-Chair, OSGi Alliance  (@OSGiAlliance)



-- 
Karl Pauls
karlpa...@gmail.com

Re: [contribution] a Logback integration with OSGi Log 1.4

[Raymond Auge]

As promised here's the repo https://github.com/rotty3000/osgi.to.logback

- Ray

On Thu, Apr 12, 2018 at 7:23 AM, Simon Chemouil  wrote:

> Hi,
>
> This sounds great. I'd probably use it! I usually use logback with
> static loggers but I might migrate (back) to OSGi Log 1.4 and that seems
> like a nice way to do this smoothly.
>
> Simon
>
>
> Raymond Auge a écrit le 11/04/2018 à 19:08 :
> > Hello everyone,
> >
> > I'm wondering if there would be interest in the felix project to accept
> and
> > host a small integration between the upcoming Log 1.4 specification with
> > Logback backend.
> >
> > The features I have already are:
> >
> > - single bundle impl
> > - generic LogListener that attempts to be the shortest path from the log
> > record (LogEntry) creation to the Logback appenders (no intermediaries)
> > - fully integrates all the record details like location, stackframes,
> etc.
> > - allows Logback to manage levels for legacy framework, service and
> bundle
> > events in a granular fashion by using canonical logger names
> > - can react to Logback scan (i.e. autoupdate) to dynamically apply level
> > changes using the new LoggingAdmin
> > - fully supports all other logback configuration goodness
> > - makes it very simply pipe all the various Log APIs to the same
> appenders
> > (or not) using the same formats (or not) and control all their log levels
> > in one place: slf4j is native, but I've tested with log4j 1.2/2.x,
> > commons-logging, JUL, jboss-logging in the same framework
> >
> > Of course Felix doesn't have a Log 1.4 impl yet so that is a
> consideration.
> >
> > This small integration has solved so many of the rather bothersome
> logging
> > issues I've been suffering the past years and I'd like to share it with
> > others.
> >
> > Sincerely,
> >
>
>


-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)
Board Member & EEG Co-Chair, OSGi Alliance  (@OSGiAlliance)

Re: [contribution] a Logback integration with OSGi Log 1.4

[Simon Chemouil]

Hi,

This sounds great. I'd probably use it! I usually use logback with
static loggers but I might migrate (back) to OSGi Log 1.4 and that seems
like a nice way to do this smoothly.

Simon


Raymond Auge a écrit le 11/04/2018 à 19:08 :
> Hello everyone,
> 
> I'm wondering if there would be interest in the felix project to accept and
> host a small integration between the upcoming Log 1.4 specification with
> Logback backend.
> 
> The features I have already are:
> 
> - single bundle impl
> - generic LogListener that attempts to be the shortest path from the log
> record (LogEntry) creation to the Logback appenders (no intermediaries)
> - fully integrates all the record details like location, stackframes, etc.
> - allows Logback to manage levels for legacy framework, service and bundle
> events in a granular fashion by using canonical logger names
> - can react to Logback scan (i.e. autoupdate) to dynamically apply level
> changes using the new LoggingAdmin
> - fully supports all other logback configuration goodness
> - makes it very simply pipe all the various Log APIs to the same appenders
> (or not) using the same formats (or not) and control all their log levels
> in one place: slf4j is native, but I've tested with log4j 1.2/2.x,
> commons-logging, JUL, jboss-logging in the same framework
> 
> Of course Felix doesn't have a Log 1.4 impl yet so that is a consideration.
> 
> This small integration has solved so many of the rather bothersome logging
> issues I've been suffering the past years and I'd like to share it with
> others.
> 
> Sincerely,
> 

Re: [contribution] a Logback integration with OSGi Log 1.4

[Raymond Auge]

I will publish it temporarily to my github account and link it.

- Ray


On Wed, Apr 11, 2018 at 5:10 PM, Karl Pauls  wrote:

> I think that sounds interesting. I'm sure we will have a Log 1.4
> implementation eventually and this might be handy no matter what.
>
> Is this available somewhere already to look at?
>
> regards,
>
> Karl
>
> On Wed, Apr 11, 2018 at 7:08 PM, Raymond Auge 
> wrote:
> > Hello everyone,
> >
> > I'm wondering if there would be interest in the felix project to accept
> and
> > host a small integration between the upcoming Log 1.4 specification with
> > Logback backend.
> >
> > The features I have already are:
> >
> > - single bundle impl
> > - generic LogListener that attempts to be the shortest path from the log
> > record (LogEntry) creation to the Logback appenders (no intermediaries)
> > - fully integrates all the record details like location, stackframes,
> etc.
> > - allows Logback to manage levels for legacy framework, service and
> bundle
> > events in a granular fashion by using canonical logger names
> > - can react to Logback scan (i.e. autoupdate) to dynamically apply level
> > changes using the new LoggingAdmin
> > - fully supports all other logback configuration goodness
> > - makes it very simply pipe all the various Log APIs to the same
> appenders
> > (or not) using the same formats (or not) and control all their log levels
> > in one place: slf4j is native, but I've tested with log4j 1.2/2.x,
> > commons-logging, JUL, jboss-logging in the same framework
> >
> > Of course Felix doesn't have a Log 1.4 impl yet so that is a
> consideration.
> >
> > This small integration has solved so many of the rather bothersome
> logging
> > issues I've been suffering the past years and I'd like to share it with
> > others.
> >
> > Sincerely,
> > --
> > *Raymond Augé* 
> >  (@rotty3000)
> > Senior Software Architect *Liferay, Inc.* 
> >  (@Liferay)
> > Board Member & EEG Co-Chair, OSGi Alliance 
> (@OSGiAlliance)
>
>
>
> --
> Karl Pauls
> karlpa...@gmail.com
>



-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)
Board Member & EEG Co-Chair, OSGi Alliance  (@OSGiAlliance)

Re: [contribution] a Logback integration with OSGi Log 1.4

[Karl Pauls]

I think that sounds interesting. I'm sure we will have a Log 1.4
implementation eventually and this might be handy no matter what.

Is this available somewhere already to look at?

regards,

Karl

On Wed, Apr 11, 2018 at 7:08 PM, Raymond Auge  wrote:
> Hello everyone,
>
> I'm wondering if there would be interest in the felix project to accept and
> host a small integration between the upcoming Log 1.4 specification with
> Logback backend.
>
> The features I have already are:
>
> - single bundle impl
> - generic LogListener that attempts to be the shortest path from the log
> record (LogEntry) creation to the Logback appenders (no intermediaries)
> - fully integrates all the record details like location, stackframes, etc.
> - allows Logback to manage levels for legacy framework, service and bundle
> events in a granular fashion by using canonical logger names
> - can react to Logback scan (i.e. autoupdate) to dynamically apply level
> changes using the new LoggingAdmin
> - fully supports all other logback configuration goodness
> - makes it very simply pipe all the various Log APIs to the same appenders
> (or not) using the same formats (or not) and control all their log levels
> in one place: slf4j is native, but I've tested with log4j 1.2/2.x,
> commons-logging, JUL, jboss-logging in the same framework
>
> Of course Felix doesn't have a Log 1.4 impl yet so that is a consideration.
>
> This small integration has solved so many of the rather bothersome logging
> issues I've been suffering the past years and I'd like to share it with
> others.
>
> Sincerely,
> --
> *Raymond Augé* 
>  (@rotty3000)
> Senior Software Architect *Liferay, Inc.* 
>  (@Liferay)
> Board Member & EEG Co-Chair, OSGi Alliance  (@OSGiAlliance)



-- 
Karl Pauls
karlpa...@gmail.com