[
https://issues.apache.org/jira/browse/UIMA-5381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor resolved UIMA-5381.
----------------------------------
Resolution: Fixed
> uv3 tooling - specify JUL logger
> --------------------------------
>
> Key: UIMA-5381
> URL: https://issues.apache.org/jira/browse/UIMA-5381
> Project: UIMA
> Issue Type: Improvement
> Components: Core Java Framework, Tools
> Affects Versions: 3.0.0SDK-alpha02
> Reporter: Marshall Schor
> Assignee: Marshall Schor
> Priority: Minor
> Fix For: 3.0.0SDK-beta
>
>
> For most common tools, insure the logger is set up, to use the JUL logger as
> a default.
> Make this work only if a JVM property,
> "-Duima.use_jul_as_default_uima_logger" is specified.
> This should work only for the uima logger, when the normal slf4j
> implementation hasn't been overridden; in that case, if slf4j finds there's
> no back end logger specified, it will set up a NOP back end. In this case,
> arrange for the UIMA logger to get the alternate JUL (java.util.logging)
> logger, instead of the slf4j (which will remain hooked up to the NOP back end
> logger).
> Update the scripts that run tools (the runUimaClass.bat and .sh) to define
> this JVM property when starting UIMA tooling, so that tools started using the
> default scripts will have some logging, if no back end is specified.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
