On 15.02.2017, at 16:33, Marshall Schor <[email protected]> wrote: > >>> If so, it seems we need to have some way to package UIMA to have this >>> user-getting-started configuration by default, which can be stripped out for >>> case (a). Does this sound right? >> I'm not sure I understand the problem. The UIMA logging framework >> already now uses different kinds of backends. By default, the >> JSR47Logger_impl backend is used (aka Java Utility Logging). > > I think this is the problem, because this default is not dependent on an > embedding context's logging setup.
The embedding context is bound to run on a JRE. So it is a matter of the embedder to configure the JRE logging facilities to do what he wants. One option would be to install a JUL-to-SLF4J bridge. Then the JUL logging would be forwarded to whatever logging backend the user uses. Unfortunately, AFAIK installing a bridge for JUL requires actual code to be invoked (dropping in a JAR doesn't seem to suffice). That is why I personally so far prefer logging against the Apache Commons Logging API which is easier to redirect. If we switch entirely to SLF4J for UIMA or even if we just used a SLF4J implementation as the default backend for the UIMA logging layer, this problem should be greatly mitigated. -- Richard
