[jitsi-dev] Request for later support of log4j


#1

Hi,

Currently, Jitsi is delivered with version 1.2.8 of log4j.jar.

Can that be upped to anything > 1.2.12?
(this added the TRACE-level back in 2005 and later-versioned libs like
"slf4j" depend on that).

Thanks in advance,
    Tom Uijldert.


#2

Sure, the only reason we are sticking with an old version is because we
never needed a new one.

Would you mind telling us why you need it though? We use
java.util.logging in Jitsi and we even have our own abstraction in
Jitsi's util package.

You can use those either directly, or, if you have some 3d party lib
depending on slf4j, then you could simply make slf4j to use
java.util.logging.

Am I missing something?

Emil

···

On 18.03.13, 16:40, Tom Uijldert wrote:

Hi,

Currently, Jitsi is delivered with version 1.2.8 of log4j.jar.

Can that be upped to anything > 1.2.12?
(this added the TRACE-level back in 2005 and later-versioned libs like
"slf4j" depend on that).

Thanks in advance,
    Tom Uijldert.

--
https://jitsi.org


#3

It's a classic inter-dependency problem.

Attempting to integrate the msrp library, it uses slf4j in order to
integrate with any (log4j in this case) log system (probably not unlike your
abstraction).

The msrp lib uses slf4j 1.5.8+, which leads to
(http://www.slf4j.org/codes.html#log4j_version) this error/problem. Hence
the need for a later version.

Btw., I tried to simply replace the log4j.jar in the lib directory with a
newer version and perform a rebuild but that didn't work.
Do I need to add some more build-magic for this to work?

Cheers,
    Tom.

···

-----Original Message-----
From: Emil Ivov [mailto:emcho@jitsi.org]

Sure, the only reason we are sticking with an old version is because we
never needed a new one.

Would you mind telling us why you need it though? We use
java.util.logging in Jitsi and we even have our own abstraction in
Jitsi's util package.

You can use those either directly, or, if you have some 3d party lib
depending on slf4j, then you could simply make slf4j to use
java.util.logging.

Am I missing something?

Emil

On 18.03.13, 16:40, Tom Uijldert wrote:
> Hi,
>
> Currently, Jitsi is delivered with version 1.2.8 of log4j.jar.
>
> Can that be upped to anything > 1.2.12?
> (this added the TRACE-level back in 2005 and later-versioned libs
like
> "slf4j" depend on that).
>
> Thanks in advance,
> Tom Uijldert.
>


#4

Hey Tom,

It's a classic inter-dependency problem.

Attempting to integrate the msrp library, it uses slf4j in order to
integrate with any (log4j in this case) log system (probably not unlike

your

abstraction).

OK, that's what I assumed, however my question is, why do you need to make
slf4j use log4j in Jitsi, when our logging system is java.util.logging?

The msrp lib uses slf4j 1.5.8+, which leads to
(http://www.slf4j.org/codes.html#log4j_version) this error/problem. Hence
the need for a later version.

Btw., I tried to simply replace the log4j.jar in the lib directory with a
newer version and perform a rebuild but that didn't work.
Do I need to add some more build-magic for this to work?

You need to copy the manifest from the original one and turn it into an
OSGi bundle.

Cheers,
Emil

--sent from my mobile

···

On Mar 20, 2013 10:10 AM, "Tom Uijldert" <tom.uijldert@gmail.com> wrote:

Cheers,
    Tom.

> -----Original Message-----
> From: Emil Ivov [mailto:emcho@jitsi.org]
>
> Sure, the only reason we are sticking with an old version is because we
> never needed a new one.
>
> Would you mind telling us why you need it though? We use
> java.util.logging in Jitsi and we even have our own abstraction in
> Jitsi's util package.
>
> You can use those either directly, or, if you have some 3d party lib
> depending on slf4j, then you could simply make slf4j to use
> java.util.logging.
>
> Am I missing something?
>
> Emil
>
> On 18.03.13, 16:40, Tom Uijldert wrote:
> > Hi,
> >
> > Currently, Jitsi is delivered with version 1.2.8 of log4j.jar.
> >
> > Can that be upped to anything > 1.2.12?
> > (this added the TRACE-level back in 2005 and later-versioned libs
> like
> > "slf4j" depend on that).
> >
> > Thanks in advance,
> > Tom Uijldert.
> >


#5

From: Emil Ivov [mailto:emcho@jitsi.org]

Hey Tom,
>
> It's a classic inter-dependency problem.
>
> Attempting to integrate the msrp library, it uses slf4j in order to
> integrate with any (log4j in this case) log system (probably not unlike

your

> abstraction).
OK, that's what I assumed, however my question is, why do you need to
make slf4j use log4j in Jitsi, when our logging system is
java.util.logging?

LOL: because I skimmed through the sources, noticed a "log4j.jar" floating
by and auto-assumed Jitsi using log4j... Live and Learn.

So, slf4j is now bridged to java.util.logging, works like a charm.
Forget I asked :slight_smile:

Cheers,
    Tom.

···

-----Original Message-----
On Mar 20, 2013 10:10 AM, "Tom Uijldert" <tom.uijldert@gmail.com> > wrote: