mirror of https://github.com/qos-ch/slf4j
minor edit
This commit is contained in:
parent
17528421bf
commit
6719babbce
|
|
@ -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.</p>
|
||||
|
|
@ -384,7 +384,7 @@ class B extends A {
|
|||
slf4j-simple-${project.version}.jar, using slf4j-simple-1.5.5.jar
|
||||
will not work.</p>
|
||||
|
||||
<p><span class="label notice">Note</span> From the client’s
|
||||
<p><span class="label notice">Note</span> From the client's
|
||||
perspective all versions of slf4j-api are compatible. Client code
|
||||
compiled with <em>slf4j-api-N.jar</em> will run perfectly fine
|
||||
with <em>slf4j-api-M.jar</em> for any N and M. You only need to
|
||||
|
|
|
|||
Loading…
Reference in New Issue