[
https://issues.apache.org/jira/browse/OODT-693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16498932#comment-16498932
]
Imesha Sudasingha edited comment on OODT-693 at 6/2/18 8:10 AM:
----------------------------------------------------------------
I think this issue is not resolved yet because we are still using JUL and SLF4J
both.
IMO, all OODT logs should go through one framework. As [~lewismc] suggested, I
too prefer SLF4J since it supports multiple underlying implementations which
can be altered according to our preferences. Furthermore, in
`java.util.logging`, we have to do string concatenation ourselves, which is
tiresome and makes the code ugly.
So, I think this should be done in near future. At least as a future GSoC
project as [~chrismattmann] mentioned. By having proper logging, OODT will be
easier to debug.
was (Author: imesha):
I think this issue is not resolved yet because we are still using JUL and SLF4J
both.
IMO, all OODT logs should go through one framework. As [~lewismc] suggested, me
too prefer SLF4J since it supports multiple underlying implementations which
can be altered according to our preferences. Furthermore, in
`java.util.logging`, we have to do string concatenation ourselves, which is
tiresome and makes the code ugly.
So, I think this should be done in near future. At least as a future GSoC
project as [~chrismattmann] mentioned. By having proper logging, OODT will be
easier to debug.
> Consolidate logging in OODT
> ---------------------------
>
> Key: OODT-693
> URL: https://issues.apache.org/jira/browse/OODT-693
> Project: OODT
> Issue Type: Improvement
> Components: file manager
> Affects Versions: 0.6
> Reporter: Lewis John McGibbney
> Priority: Major
> Fix For: 1.1
>
>
> Right now we seem to be using an array of inconsistent logging frameworks.
> Personally I really like the Slf4j over Log4j setup. Extremely easy to work
> with, easy to configure and Log4j 2.X is dynamite so if we can implement that
> then we are laughing.
> This is by no means a trivial task.
> It is however an important one.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
