You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Marshall Schor (JIRA)" <de...@uima.apache.org> on 2017/03/02 15:14:45 UTC
[jira] [Resolved] (UIMA-5343) uv3 switch logger level mappings to
match uimaFIT better
[ https://issues.apache.org/jira/browse/UIMA-5343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marshall Schor resolved UIMA-5343.
----------------------------------
Resolution: Fixed
> uv3 switch logger level mappings to match uimaFIT better
> --------------------------------------------------------
>
> Key: UIMA-5343
> URL: https://issues.apache.org/jira/browse/UIMA-5343
> Project: UIMA
> Issue Type: Improvement
> Components: Core Java Framework
> Reporter: Marshall Schor
> Fix For: 3.0.0SDK-alpha02
>
>
> UIMA Logger levels are modeled on java.util.logging.Level. This has levels: SEVERE/WARNING/INFO/CONFIG/FINE/FINER/FINEST.
> Newer loggers, including the common facade SLF4J have levels ERROR/WARN/INFO/TRACE/DEBUG.
> Because UIMA v3 is using the slf4j style as a default, it needs to have a mapping between these levels. The initial mapping needs updating slightly so that it is compatible with the already in existence mappings done by uimaFIT in its Extended Logger implementation.
> Change the mappings to:
> SEVERE <-> ERROR
> WARNING <-> WARN
> INFO <-> INFO
> CONFIG <-> INFO (distinguished by a marker, UIMA_MARKER_CONFIG)
> *FINE <-> DEBUG
> *FINER <-> TRACE
> *FINEST <-> TRACE (distinguished by a marker, UIMA_MARKER_FINEST)
> The asterisks mark the changes.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)