Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>There is some version conflict between some commons logging lib and one of the slf4j libs. <em>(This is not a maven problem, it is a problem that occures if you maintain the libs by hand too.)</em></p> <p>Open the maven pom with eclipse. There is a Tab called "hirarchy" it will show the used and required versions. Try to use a cobination of the logging liaries that does not have so much conflicts.</p> <hr> <p>I have had a look at your pom. The problem is the <code>jcl-over-slf4j-1.5.8.jar</code> it CONTAINS some org.apache.commons.loggin jars that are not compatible to slf4j 1.6.6.</p> <p><code>jcl-over-slf4j-1.5.8.jar</code> is referenced by <code>org.jasig.cas</code></p> <p>What I would try is to replace the <code>jcl-over-slf4j-1.5.8.jar</code> with <code>jcl-over-slf4j-1.6.6.jar</code></p> <pre class="lang-xml prettyprint-override"><code> &lt;dependency&gt; &lt;groupId&gt;org.jasig.cas&lt;/groupId&gt; &lt;artifactId&gt;cas-server-core&lt;/artifactId&gt; &lt;version&gt;3.5.0&lt;/version&gt; &lt;exclusions&gt; &lt;exclusion&gt; &lt;artifactId&gt;jcl-over-slf4j&lt;/artifactId&gt; &lt;groupId&gt;org.slf4j&lt;/groupId&gt; &lt;/exclusion&gt; &lt;/exclusions&gt; &lt;/dependency&gt; &lt;dependency&gt; &lt;groupId&gt;org.slf4j&lt;/groupId&gt; &lt;artifactId&gt;jcl-over-slf4j&lt;/artifactId&gt; &lt;version&gt;1.6.6&lt;/version&gt; &lt;/dependency&gt; </code></pre> <p>But I do not know cas-server-core 3.5.0 is compatible with <code>jcl-over-slf4j-1.6.6.jar</code>. But in most cases the "outer" API of an logging framework is more stable then the "inner" API that is used by the logging Bridges. -- So good luck.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload