Mailing-List: contact stanbol-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: stanbol-dev@incubator.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <4DC15990.3090503@istc.cnr.it>
Date: Wed, 04 May 2011 15:50:08 +0200
From: Alessandro Adamou <alessandro.adamou@istc.cnr.it>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-GB;
 rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: stanbol-dev@incubator.apache.org
Subject: SLF4J bindings
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Hi,

I started to get SLF4J-related errors when running Kres unit tests these 
days. Stuff like

---
SLF4J: slf4j-api 1.6.x (or later) is incompatible with this binding.
SLF4J: Your binding is version 1.5.5 or earlier.
SLF4J: Upgrade your binding to version 1.6.x. or 2.0.x
---

Tests won't run at all. Some failures occur when testing via Eclipse, 
others with Maven.

A mvn dependency:tree on the Stanbol root says that most Stanbol 
components are using 1.6.1 where I'm sitting today, as their POMs don't 
seem to specify a version.

We had forced version 1.5.2 for Kres bundles, both with slf4j-api and 
its bindings. Could it be time to stop depending on it? And what binding 
is best to adopt between slf4j-simple and slf4j-log4j12 ?

I don't think we have to stick to a specific version or binding, so long 
as the API stays compatible.

Cheers

Alessandro

-- 
M.Sc. Alessandro Adamou

Alma Mater Studiorum - Universit� di Bologna
Department of Computer Science
Mura Anteo Zamboni 7, Bologna - Italy

Semantic Technology Laboratory (STLab)
Institute for Cognitive Science and Technology (ISTC)
National Research Council (CNR)
Via Nomentana 56, 00161 Rome - Italy


"As for the charges against me, I am unconcerned. I am beyond their timid, lying morality, and so I am beyond caring."
(Col. Walter E. Kurtz)