From 604a9f077d5081865a7189124a17a840d2a83d42 Mon Sep 17 00:00:00 2001 From: David Syer Date: Fri, 4 Dec 2009 16:15:20 +0000 Subject: [PATCH] SPR-5327: update artifact ids --- spring-framework-reference/src/overview.xml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/spring-framework-reference/src/overview.xml b/spring-framework-reference/src/overview.xml index e957bb69360..98226a64fc7 100644 --- a/spring-framework-reference/src/overview.xml +++ b/spring-framework-reference/src/overview.xml @@ -351,7 +351,7 @@ TR: OK. Added to diagram.--> scalable, fail-safe web applications that might need declarative security. -
+
Dependency Management and Naming Conventions Dependency management and dependency injection are different @@ -843,7 +843,7 @@ TR: OK. Added to diagram.--> </dependency> <dependency> <groupId>org.slf4j</groupId> - <artifactId>jcl-slf4j</artifactId> + <artifactId>jcl-over-slf4j</artifactId> <version>1.5.8</version> <scope>runtime</scope> </dependency> @@ -878,7 +878,7 @@ TR: OK. Added to diagram.--> and generates fewer dependencies, is to bind directly to Logback. This removes the extra binding step because Logback implements SLF4J directly, so you only need - to depend on two libaries not four (jcl-slf4j and + to depend on two libaries not four (jcl-over-slf4j and logback). If you do that you might also need to exlude the slf4j-api dependency from other external dependencies (not Spring), because you only want one version of that API on the classpath.