[
https://issues.apache.org/jira/browse/OWB-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12837867#action_12837867
]
James Carman commented on OWB-300:
----------------------------------
I understand the whole idea about minimizing dependencies, but let's get real
here. If you're using OWB or some other web-based framework, you've already
got a boatload of dependencies. Adding SLF4J to the mix does buy you some
flexibility, though. What if a project doesn't want to use JUL? What if they
want all of their logging to go somewhere else? Having OWB force them to use
and configure JUL is a bigger no-no, if you ask me. OWB needs to be flexible
for the client environment. With SLF4J, the client project can use whatever
logging implementation they wish and SLF4J (and thus OWB) can adapt to it.
> Currently OWB requires log4j for logging. This patch provides a means of
> choosing other loggers.
> ------------------------------------------------------------------------------------------------
>
> Key: OWB-300
> URL: https://issues.apache.org/jira/browse/OWB-300
> Project: OpenWebBeans
> Issue Type: Improvement
> Components: Core
> Affects Versions: M4
> Environment: All
> Reporter: Paul J. Reder
> Assignee: Gurkan Erdogdu
> Priority: Minor
> Fix For: M4
>
> Attachments: OWBLoggerOnly.patch
>
>
> Currently OWB requires (is dependent on) log4j for logging. This patch
> provides a means of choosing other loggers (thus reducing the number of
> dependencies but allowing flexibility). Notably, the patch switches the
> logging code to using the JDK java util logging (which is already available
> for other reasons). The patch includes comments to show how to maintain log4j
> use or use it as a model to enable other logging libs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
