Hey guys!
I'd like to refer to THIS thread by @drgottjr, and more specifically to THIS post by @aeric.
I use SLF4J in my application and my log always showed the annoying "SLF4J: No SLF4J providers were found" message.
Although SLF4J defaults to a no-operation logger implementation, I've decided to ban this message from my logs.
In the aforementioned post by @aeric, there's THIS link (which I recommend to take a look into) to a fix to SQLIte-JDBC version 3.43.2.0.
I always use the latest SQLite-JDBC version, so now I'm using version 3.44.0.0.
My project's #AdditionalJar lines were this:
As suggested by @aeric, I've changed to:
The message "SLF4J: No SLF4J providers were found" is gone!
Thanks, @aeric, for this valuable hint!
I'd like to refer to THIS thread by @drgottjr, and more specifically to THIS post by @aeric.
I use SLF4J in my application and my log always showed the annoying "SLF4J: No SLF4J providers were found" message.
Although SLF4J defaults to a no-operation logger implementation, I've decided to ban this message from my logs.
In the aforementioned post by @aeric, there's THIS link (which I recommend to take a look into) to a fix to SQLIte-JDBC version 3.43.2.0.
I always use the latest SQLite-JDBC version, so now I'm using version 3.44.0.0.
My project's #AdditionalJar lines were this:
B4X:
#AdditionalJar: slf4j-api-2.0.9
#AdditionalJar: slf4j-jdk14-2.0.9
#AdditionalJar: slf4j-nop-2.0.9
As suggested by @aeric, I've changed to:
B4X:
#AdditionalJar: slf4j-api-1.7.9
#AdditionalJar: slf4j-jdk14-1.7.9
#AdditionalJar: slf4j-nop-1.7.9
The message "SLF4J: No SLF4J providers were found" is gone!
Thanks, @aeric, for this valuable hint!