[
https://issues.apache.org/jira/browse/PIVOT-882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13731339#comment-13731339
]
Sandro Martini commented on PIVOT-882:
--------------------------------------
Hi Roger,
yes I agree with all your points ... so I think that a direct usage of
Commons-Logging (even if no more used in many Web Applications, for many
reasons ...) for us could be good, because for sure we need a general way to
log..
So a plan could be to add a dependency on it for 2.1, and start use it, for
example replacing our System.out/err calls ... but do you prefer a direct
usage, or with a Pivot wrapper (LogManager or similar) ?
Then, probably there are many other things useful to log inside Pivot, for
example when doing any query via HTTP, etc ... but this could be expanded even
later, in 2.5 .
Be free to reassign to you if you have some idea/skeleton.
Maybe some discussion on dev mailing list (with a reference to this issue)
could be good to get more feedback.
> 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
