Could we explicitly set all the sl4j artifact versions to 1.4.3? This has caused me many issues as well.
- Dan

Daniel Kulp wrote:
On Tuesday 25 September 2007, Christopher Moesel wrote:
  
It looks like the pom.xml for the http-jetty transport includes a
dependency on slf4j-jdk14 v1.3.1.  This recently caused me issues as I
am using slf4j v1.4.3 and it is apparently incompatible with v1.3.1.

I'm not familiar with that part of the code (the http-jetty
transport)...

- My understanding was that CXF is not using SLF4J, so is this
dependency needed?  Is it for Jetty (since Jetty uses SLF4J)?
    

Yea.  Jetty uses it.

  
- If it is needed, could we bump the version up to 1.4.3?
    

I'd rather not.   Jetty specifically states that they want 1.3.1:
http://repo1.maven.org/maven2/org/mortbay/jetty/project/6.1.5/project-6.1.5.pom
    <slf4j-version>1.3.1</slf4j-version>

For the CXF distribution, I'd rather make sure we're using the same 
versions that they are testing and building with if at all possible.

For you, you could just add a dependency to the 1.4.3 version in your 
pom.  Recent mavens (2.0.6+) should then use that version instead.   
Alternatively, you can exclude it via normal maven exclusions.


  


-- 
Dan Diephouse
MuleSource
http://mulesource.com | http://netzooid.com/blog

Reply via email to