On Wed, Mar 13, 2024 at 11:07 PM Grzegorz Grzybek
wrote:
> I hope this helps.
>
> regards
> Grzegorz Grzybek
>
> It looks helpful, I'll take a stab at it next week and follow up. Thank
you.
Regards,
Will Hartung
: Thursday, 14 March 2024 07:07
To: user@karaf.apache.org
Subject: Re: Karaf log4j conflict
Hello
So, for this fragment, do I simply need to make a fragment containing the extra
log4j information, or do I need to extract the code that is using those log4j
pieces and put that into a fragment
Hello
So, for this fragment, do I simply need to make a fragment containing the
> extra log4j information, or do I need to extract the code that is using
> those log4j pieces and put that into a fragment. That seems to be a much
> taller order. Compared to bolting the necessary log4j.core classes
On Wed, Mar 13, 2024 at 10:35 AM Jean-Baptiste Onofré
wrote:
> Hi Will
>
> Did you take a look on
>
> https://github.com/apache/karaf/tree/main/examples/karaf-log-appender-example
> ?
>
> Generally speaking, the org.apache.logging* packages should be
> imported in your bundle. The fragment would
Hi Will
Did you take a look on
https://github.com/apache/karaf/tree/main/examples/karaf-log-appender-example
?
Generally speaking, the org.apache.logging* packages should be
imported in your bundle. The fragment would extend an existing bundle
classloader with your classes.
Maybe if you share a
On Mon, Mar 11, 2024 at 11:33 PM Grzegorz Grzybek
wrote:
> Hello
>
> Pax Logging (where pax-logging-api contains and exports Logging APIs,
> while pax-logging-log4j2 is the Log4j2-based implementation) has enormous
> amount of effort put into integration of very different logging packages
> and
Hello
Pax Logging (where pax-logging-api contains and exports Logging APIs, while
pax-logging-log4j2 is the Log4j2-based implementation) has enormous amount
of effort put into integration of very different logging packages and it is
used by Apache Karaf among others.
The team developed Pax
