[
https://issues.apache.org/jira/browse/GORA-77?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187176#comment-13187176
]
Lewis John McGibbney commented on GORA-77:
------------------------------------------
Well you're absolutely correct, this ties in with my own experience as well as
the bulk of the projects I've worked on utilise an Slf4j over Log4j approach, I
suppose if we agree then this issue should be renamed accordingly.
Put simply my justification to change this would be the following:
- Slf4j would enable us with the logging abstraction, if users were not happy
with Log4j they could change this accordingly within their own implementations.
- Log4j provides us with a easily to tune, fine grained logger. Again depending
on how a user wishes to implement logging within their Gora deployment, and the
subsequent cost the can afford to do logging they can easily change the
granularity.
I must be open that I personally have not much experience working with commons
logging, I've always had good experiences working with Slf4j & Log4j. Although
it may sound slightly illogical to change something that isn't broken, I hope
that the two points highlighted above would justify this issue.
wdyt?
Thanks
> Replace commons logging with Log4j
> ----------------------------------
>
> Key: GORA-77
> URL: https://issues.apache.org/jira/browse/GORA-77
> Project: Gora
> Issue Type: Improvement
> Components: documentation
> Affects Versions: 0.1.1-incubating
> Reporter: Lewis John McGibbney
> Priority: Minor
> Fix For: 0.2-incubating
>
>
> Log4j provides a richer logging resource, Gora would benefit accordingly. I
> propose to implement Log4j 1.2.16 to replace all commons logging imports and
> code.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
