I'm willing to classify this as not a blocker. UIMA V3 changed the logging setup - v2 used the built-into-java logger, v3 uses slf4j, which adds an indirection, which can use the built-in java logger, or integrate with others.
The normal mechanism to control this is to include some jar that specifies what slf4j should integrate with. If nothing is specified, I think you get messages like: SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. SLF4J: Failed to load class "org.slf4j.impl.StaticMDCBinder". SLF4J: Defaulting to no-operation MDCAdapter implementation. SLF4J: See http://www.slf4j.org/codes.html#no_static_mdc_binder for further details. I see these messages in the console when running the Ruta interpreter. The consequence of this is that no logging is being done... To fix this, you can either add the slf4j logger jar you want to the classpath, or, when you launch Java, you can include the -D parameter: -Duima.use_jul_as_default_uima_logger (see https://uima.apache.org/d/uimaj-current/references.html#ugr.ref.config.property-table <http://uima.apache.org/d/uimaj-current/references.html#ugr.ref.config.property-table>) -Marshall
