From 6719babbce4fdb9c1c587f45d2129a55fd74caaa Mon Sep 17 00:00:00 2001 From: Ceki Gulcu Date: Wed, 16 Oct 2019 20:32:17 +0200 Subject: [PATCH] minor edit --- slf4j-site/src/site/pages/codes.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/slf4j-site/src/site/pages/codes.html b/slf4j-site/src/site/pages/codes.html index 20279988..44a599c2 100755 --- a/slf4j-site/src/site/pages/codes.html +++ b/slf4j-site/src/site/pages/codes.html @@ -362,7 +362,7 @@ class B extends A { declare a dependency on any SLF4J binding but only depend on slf4j-api. When a library declares a compile-time dependency on a SLF4J binding, it imposes that binding on the end-user, thus - negating SLF4J’s purpose. When you come across an embedded + negating SLF4J's purpose. When you come across an embedded component declaring a compile-time dependency on any SLF4J binding, please take the time to contact the authors of said component/library and kindly ask them to mend their ways.

@@ -384,7 +384,7 @@ class B extends A { slf4j-simple-${project.version}.jar, using slf4j-simple-1.5.5.jar will not work.

-

Note From the client’s +

Note From the client's perspective all versions of slf4j-api are compatible. Client code compiled with slf4j-api-N.jar will run perfectly fine with slf4j-api-M.jar for any N and M. You only need to