[
https://issues.apache.org/jira/browse/OWB-300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul J. Reder updated OWB-300:
------------------------------
Description: 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. (was: Currently OWB
requires log4j for logging. This patch provides a means of choosing other
loggers. Notably, the patch switches the logging code to using the JDK java
util logging. The patch includes comments to show how to maintain log4j use or
use it as a model to enable other logging libs.)
> 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.
