[
https://issues.apache.org/jira/browse/PIVOT-882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13730938#comment-13730938
]
Roger Whitcomb commented on PIVOT-882:
--------------------------------------
Yes I am. I have been following discussions on Apache Commons mailings lists
about logging frameworks, and (still) problems related to classloading in
Commons Logging. But, I am a strong believer in using our own stuff, so I
really think we should (if we're going to use any logging framework at all),
use either built-in Java logging, or use Apache Commons Logging (which does
allow delegation to other logging frameworks).
This does, of course, introduce a new runtime dependency on either the
"commons-logging-api....jar" or "commons-logging....jar" files that must be
shipped with Pivot.
Steven's points about SLF4J, etc. are well-founded, but I think the problems
that still exist in Commons Logging with respect to classloading issues are not
very important for Pivot because we are not a library that will potentially
exist inside other applications and then inside application servers (think
Tomcat, etc.) which all might have different or conflicting logging
implementations. A Pivot application (be it a Desktop App or Browser Applet)
will maybe make use of 3rd party libraries itself, but the existing frameworks
(except JUL) can integrate well with each other. In other words, if we choose
Apache Commons Logging (ACL) for Pivot itself, then if an application designer
wants to use SLF4J. and also needs to use a 3rd party library that uses JUL,
then ACL can be configured to defer to JUL or SLF4J, so there is no real
conflict.
> Internal Logging Mechanism
> --------------------------
>
> Key: PIVOT-882
> URL: https://issues.apache.org/jira/browse/PIVOT-882
> Project: Pivot
> Issue Type: Improvement
> Affects Versions: 2.0, 2.0.1, 2.0.2
> Reporter: Steven Swor
> Assignee: Sandro Martini
> Priority: Minor
> Labels: logging
> Fix For: 2.5, 2.1
>
>
> As of 2.0.2, Pivot does some internal logging using calls to System.out and
> System.err (for example, when using org.apache.pivot.json.JSONSerializer with
> verbose = true).
> It would be really nice if Pivot could leverage a more robust logging API
> instead, but certain design decisions come into play when choosing a logging
> framework.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
