Refine documentation on logging

docs/getting-into-the-code/code-howtos.md

@@ -119,7 +119,8 @@ If you want to catch the event you'll have to register your listener class with
 
 ## Logging
 
-JabRef uses the logging facade [SLF4j](https://www.slf4j.org/). All log messages are passed internally to [log4j2](https://logging.apache.org/log4j/2.x/) which handles any filtering, formatting and writing of log messages.
+JabRef uses the logging facade [SLF4j](https://www.slf4j.org/).
+All log messages are passed internally to [tinylog](https://tinylog.org/v2/) which handles any filtering, formatting and writing of log messages.
 
 * Obtaining a logger for a class:
 
@@ -137,6 +138,11 @@ JabRef uses the logging facade [SLF4j](https://www.slf4j.org/). All log messages
   ```
 
 * SLF4J also support parameterized logging, e.g. if you want to print out multiple arguments in a log statement use a pair of curly braces. [Examples](https://www.slf4j.org/faq.html#logging_performance)
+* When running tests, `tinylog-debug.properties` is used.
+  As default, only `info` is logged.
+  When developing, it makes sense to use `debug` as log level.
+  One can change the log level per class using the pattern `level@class=debug` is set to `debug`.
+  In the `.properties` file, this is done for `org.jabref.model.entry.BibEntry`.
 
 ## Using Localization correctly
 

src/main/java/org/jabref/model/entry/BibEntry.java

@@ -469,7 +469,7 @@ private Optional<String> genericGetFieldOrAlias(Field field, BiFunction<BibEntry
                 }
             } else {
                 // Date field not in valid format
-                LOGGER.debug("Could not parse date " + date.get());
+                LOGGER.debug("Could not parse date {}", date.get());
                 return Optional.empty();
             }
         }

src/test/resources/tinylog-test.properties

@@ -1,2 +1,3 @@
 level = info
 writer = console
+[email protected] = debug