[
https://issues.apache.org/jira/browse/UIMA-5556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16161872#comment-16161872
]
Richard Eckart de Castilho commented on UIMA-5556:
--------------------------------------------------
IMHO from a i18n perspective, it wasn't a stellar idea to drop the parameter
positions in SLF4J. To get i18n back, apparently the suggestion is to add yet
another wrapper around SLF4J which then also adds back the parameter positions:
https://www.slf4j.org/localization.html
Given that UIMA even supports localizable exceptions, it might be conceptually
more consistent to prefer an approach where we retain the parameter positions.
> uv3: Logging substitution does not work consistently
> ----------------------------------------------------
>
> Key: UIMA-5556
> URL: https://issues.apache.org/jira/browse/UIMA-5556
> Project: UIMA
> Issue Type: Bug
> Components: Core Java Framework
> Affects Versions: 3.0.0SDK-beta
> Reporter: Richard Eckart de Castilho
>
> The substitution of values in UIMA logging does not work consistently. E.g.
> for the following code
> {noformat}
> UIMAFramework.getLogger().warn("Skipping adding \"{0}\" to URLs", p);
> {noformat}
> Depending on the configured logging backend, I get different messages. E.g.
> with SLF4J, I get the broken:
> {noformat}
> 2017-09-08 14:45:42 WARN [main] (Misc) - Skipping adding "{0}" to URLs
> {noformat}
> while with what (I suppose) is the default UIMA logger used in the uimaFIT
> maven plugin, I get the correct
> {noformat}
> [WARNING] Skipping adding "" to URLs
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
