[ https://issues.apache.org/jira/browse/PROTON-343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rafael H. Schloming updated PROTON-343: --------------------------------------- Fix Version/s: (was: 0.6) 0.7 > Add a pluggable Proton logging layer > ------------------------------------ > > Key: PROTON-343 > URL: https://issues.apache.org/jira/browse/PROTON-343 > Project: Qpid Proton > Issue Type: Improvement > Components: proton-c, proton-j > Reporter: Philip Harvey > Assignee: Philip Harvey > Fix For: 0.7 > > Attachments: > 0001-PROTON-343-sketched-out-the-Java-parts-of-the-propos.patch > > > Applications that use Proton sometimes want Proton to produce logging. > Goals > ==== > * Proton should provide a default logging implementation. > * It should be easy for Proton client code to provide custom logging > implementation, e.g. one that uses the same third party logging framework as > their application code. > * Proton should not have a compile-time dependency on a third party logging > framework > * Proton's log output is considered to be part of its public interface. > Therefore, in the spirit of Proton's cross-language consistency goals, this > output should be consistent between proton-c and proton-j. > * The goals that general-purpose logging frameworks try to meet - > performance, ease of use etc - also apply. -- This message was sent by Atlassian JIRA (v6.1.5#6160)