[
https://issues.apache.org/jira/browse/OOZIE-2702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16121400#comment-16121400
]
Peter Cseh edited comment on OOZIE-2702 at 8/10/17 10:27 AM:
-------------------------------------------------------------
We have to be careful about this. The launcherAM should be compatible with a
wide range of logging frameworks. It would make sense to even use the built-in
java logging api only. Conflicting logging libraries can result in no logs at
all figuring out the issue very hard
was (Author: gezapeti):
We have to be careful about this. The launcherAM should be compatible with a
wide range of logging frameworks. It would make sense to even use the built-in
java logging api only.
> OYA: Remove System.out.println() calls and replace them with Loggers
> --------------------------------------------------------------------
>
> Key: OOZIE-2702
> URL: https://issues.apache.org/jira/browse/OOZIE-2702
> Project: Oozie
> Issue Type: Sub-task
> Reporter: Peter Bacsko
>
> Currently there are a lot of {{System.out.println()}} calls in the code,
> mostly in the {{sharelib}}.
> This solution is inferior to using a logger library, where we can fine-tune a
> lot of different things. It's desirable that we migrate these calls to a
> logging framework.
> The preferred solution would be to use a {{Logger}} in our code, redirected
> per default to the console using {{ConsoleAppender}}. That way we wouldn't be
> breaking compatibility, but some of the users could redirect to another
> {{Appender}} s.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
