[
https://issues.apache.org/jira/browse/UIMA-5556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16161861#comment-16161861
]
Marshall Schor commented on UIMA-5556:
--------------------------------------
I'm thinking of this approach:
1) For backwards compatibility, support UIMA logger calls as before, manually
doing the substitute calls before passing the message on.
2) for new logging APIs, support the {} syntax only, for faster logging, and
being consistent with current logging styles.
The new logging apis are things like logger.warn, logger.info, etc. rather than
logger.log(Level.INFO, ...).
Because these APIs are new, no backwards compatibility issue exists (for uima
loggers), and this is more consistent if the users are already using modern
loggers.
Does this seem OK?
> 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)
