Update SLF4J to 2.0
Current DMX platform (5.3.3) comes with SLF4J 1.7 deployed, a logging facade. Tess4J (#532 (closed)) needs SLF4J 2.0.
https://www.slf4j.org/manual.html
Unfortunately this is not an easy upgrade. SLF4J API version 2.0.0 relies on Java's ServiceLoader mechanism to find its logging backend, and this mechanism is known for not working well with OSGi
https://blog.osgi.org/2013/02/javautilserviceloader-in-osgi.html
As a solution we can utilize Apache Aries SPI Fly component, an implementation of the OSGi ServiceLoader Mediator specification.
https://aries.apache.org/documentation/modules/spi-fly.html
SPI Fly does his job by Java byte code manipulation dynamically at plugin deployment time, in order to replace all ServiceLoader calls with an OSGi compliant logic. Byte code manipulation is done by ObjectWeb ASM.
https://asm.ow2.io
As logging is a cross-cutting concern it needs to be deployed at platform level (in contrast to plugin level). So with upcoming 5.3.4 the DMX standard installation will come with a whole lot of new dependencies, just to do logging
@jpn FYI