[
https://issues.apache.org/jira/browse/PIVOT-882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13734076#comment-13734076
]
Sandro Martini commented on PIVOT-882:
--------------------------------------
Ok, +1 even from me for Log4J 2 ... and probably someone of us should tell them
that we are doing it :-) ...
And even ask for the when they (approximatively) they thing 2.0 final will be
released ... I don't like too much to depend on beta products.
This could tell us if include this feature in 2.1 or in 2.5 ... do you agree ?
> 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
