From 956acb06d62ac33f975f312819b929bcdfbc70fa Mon Sep 17 00:00:00 2001
From: Ceki Gulcu Limiting the transitivity of the SLF4J provider used in your
@@ -730,7 +730,7 @@ The first dependency declaration essentially states that
@@ -807,6 +807,10 @@ Generalities
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-api</artifactId>
- <version>${project.version}</version>
+ <version>${latest.stable.version}</version>
</dependency>
Generalities
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-log4j12</artifactId>
- <version>${project.version}</version>
+ <version>${latest.stable.version}</version>
<scope>test</scope>
</dependency>
@@ -787,7 +787,7 @@ Generalities
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>jcl-over-slf4j</artifactId>
- <version>${project.version}</version>
+ <version>${latest.stable.version}</version>
</dependency>
Generalities
alternative 3) empty artifacts
+ +Version99 service will be disabled at the of + 2022.
+An alternative approach is to depend on an empty
commons-logging.jar artifact. This clever Generalities
The empty artifact is available from a http://version99.qos.ch a
- high-availability Maven repository, replicated on several hosts
- located in different geographical regions.
The following declaration adds the version99 repository to the set of remote repositories searched by Maven. This @@ -863,7 +867,7 @@
since 1.6.0 If no binding is found on the class path, then SLF4J will default to a no-operation