slf4J version problem

[Gérard Dupont <ge...@gmail.com>]

Hi all,

I'm trying to use the jackRabbit WebDav client. So I downloaded the source
and deployed the jackRabbit artifact on my maven repository. But when I'm
trying to embed the jackRabbit WebDav client, I got a SLF4J versionning
conflict. Checking dependencies, I found:

[INFO] +- org.apache.jackrabbit:jackrabbit-webdav:jar:2.3-SNAPSHOT:compile
[INFO] |  +- org.slf4j:slf4j-api:jar:1.5.6:compile
[INFO] |  +- commons-httpclient:commons-httpclient:jar:3.0:compile
[INFO] |  |  \- commons-codec:commons-codec:jar:1.2:compile
[INFO] |  \- org.slf4j:jcl-over-slf4j:jar:1.6.1:compile

So obviously, the commons-httpclient is using version 1.6.1 of the API which
is not compatible with the 1.5.6... Is it a known problem on the trunk ?

-- 
Gérard Dupont
Information Processing Control and Cognition (IPCC)
CASSIDIAN - an EADS company

Document & Learning team - LITIS Laboratory

Re: slf4J version problem

[Gérard Dupont <ge...@gmail.com>]

Hi Alex,

On 1 April 2011 19:03, Alex Parvulescu <al...@gmail.com> wrote:

> Hi Gérard,
>
> This may be a stupid question, when you did a build of the JR WebDav
> client, did you update the parent pom, too?
>

for sure ;-)


> That is in Jackrabbit-parent, at the same level with jackrabbit-webdav.
> That is where the slf4j versions are stored.
> Another option, (where I've seen this once) is when mixing components of JR
> 2.3 with 2.2.X which depend on an older slf4j version.
>
> Also, commons-httpclient is using commons-logging for logging, not slf4j.
> Which was taken out and replaced with jcl-over-slf4j, so that cannot be the
> problem you have.
>

I'm not sure where the problem was but I'm sure that I solved it using the
last tagged version. For sure this one is more stable ;-)


>  As a reference see [1] for when the logging migration work started.
>
[1] https://issues.apache.org/jira/browse/JCR-2411
>

I'll have a look.



-- 
Gérard Dupont
Information Processing Control and Cognition (IPCC)
CASSIDIAN - an EADS company

Document & Learning team - LITIS Laboratory

Re: slf4J version problem

[Alex Parvulescu <al...@gmail.com>]

Hi Gérard,

This may be a stupid question, when you did a build of the JR WebDav client,
did you update the parent pom, too? That is in Jackrabbit-parent, at the
same level with jackrabbit-webdav. That is where the slf4j versions are
stored.
Another option, (where I've seen this once) is when mixing components of JR
2.3 with 2.2.X which depend on an older slf4j version.

Also, commons-httpclient is using commons-logging for logging, not slf4j.
Which was taken out and replaced with jcl-over-slf4j, so that cannot be the
problem you have.

As a reference see [1] for when the logging migration work started.

[1] https://issues.apache.org/jira/browse/JCR-2411

2011/4/1 Gérard Dupont <ge...@gmail.com>

> Hi all,
>
> I'm trying to use the jackRabbit WebDav client. So I downloaded the source
> and deployed the jackRabbit artifact on my maven repository. But when I'm
> trying to embed the jackRabbit WebDav client, I got a SLF4J versionning
> conflict. Checking dependencies, I found:
>
> [INFO] +- org.apache.jackrabbit:jackrabbit-webdav:jar:2.3-SNAPSHOT:compile
> [INFO] |  +- org.slf4j:slf4j-api:jar:1.5.6:compile
> [INFO] |  +- commons-httpclient:commons-httpclient:jar:3.0:compile
> [INFO] |  |  \- commons-codec:commons-codec:jar:1.2:compile
> [INFO] |  \- org.slf4j:jcl-over-slf4j:jar:1.6.1:compile
>
> So obviously, the commons-httpclient is using version 1.6.1 of the API
> which is not compatible with the 1.5.6... Is it a known problem on the trunk
> ?
>
> --
> Gérard Dupont
> Information Processing Control and Cognition (IPCC)
> CASSIDIAN - an EADS company
>
> Document & Learning team - LITIS Laboratory
>
>