[
https://issues.apache.org/jira/browse/LOGGING-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15380699#comment-15380699
]
Remko Popma commented on LOGGING-136:
-------------------------------------
+1 to deprecate commons-logging and recommend users to upgrade to the Log4j 2
API.
> API Enhancements: 'String.format(String, Object...)' Functionality & Delegate
> Convenience Methods
> -------------------------------------------------------------------------------------------------
>
> Key: LOGGING-136
> URL: https://issues.apache.org/jira/browse/LOGGING-136
> Project: Commons Logging
> Issue Type: Improvement
> Affects Versions: 1.1.1
> Environment: N/A
> Reporter: Daniel Siviter
> Labels: api, api-addition
> Fix For: 2.0
>
> Attachments: commons-logging-1.1.1-src.rar,
> commons-logging-1.1.1.jar, site.rar
>
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> Improvements to the API to allow convenience methods for performing
> {{String.format(String, Object...)}} and allow access to the internal logging
> delegate.
> Firstly, to add the {{String#format(String, Object...)}} functionality modify
> the methods (note: only {{#trace(...)}} shown):
> {{void trace(Object message, Object... args);}}
> {{void trace(Object message, Throwable t, Object... args);}}
> This would allow compatiblity with previous versions of the API (although I
> believe they would still require a re-compile) and help tidy up code.
> Secondly, to obtain access to the internal instance of a logger the addition
> of a {{#getDeletegate()}} method.
> I can supply the code if required.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
