cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dan Diephouse <dan.diepho...@mulesource.com>
Subject Re: slf4j-jdk14 v1.3.1 in the http-jetty transport POM
Date Tue, 25 Sep 2007 21:28:33 GMT
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Could we explicitly set all the sl4j artifact versions to 1.4.3? This
has caused me many issues as well. <br>
- Dan<br>
<br>
Daniel Kulp wrote:
<blockquote cite="mid:200709251724.15091.dkulp@apache.org" type="cite">
  <pre wrap="">On Tuesday 25 September 2007, Christopher Moesel wrote:
  </pre>
  <blockquote type="cite">
    <pre wrap="">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)?
    </pre>
  </blockquote>
  <pre wrap=""><!---->
Yea.  Jetty uses it.

  </pre>
  <blockquote type="cite">
    <pre wrap="">- If it is needed, could we bump the version up to 1.4.3?
    </pre>
  </blockquote>
  <pre wrap=""><!---->
I'd rather not.   Jetty specifically states that they want 1.3.1:
<a class="moz-txt-link-freetext" href="http://repo1.maven.org/maven2/org/mortbay/jetty/project/6.1.5/project-6.1.5.pom">http://repo1.maven.org/maven2/org/mortbay/jetty/project/6.1.5/project-6.1.5.pom</a>
    &lt;slf4j-version&gt;1.3.1&lt;/slf4j-version&gt;

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.


  </pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">-- 
Dan Diephouse
MuleSource
<a class="moz-txt-link-freetext" href="http://mulesource.com">http://mulesource.com</a>
| <a class="moz-txt-link-freetext" href="http://netzooid.com/blog">http://netzooid.com/blog</a></pre>
</body>
</html>

Mime
View raw message