[jboss-jira] [JBoss JIRA] Updated: (JBLOGGING-58) Support setting the logging provider explicitly

[David Lloyd (JIRA)]

     [ https://issues.jboss.org/browse/JBLOGGING-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Lloyd updated JBLOGGING-58:
---------------------------------

    Fix Version/s: 3.0.0.CR1
                       (was: 3.0.0.Beta5-jboss-logging)


> Support setting the logging provider explicitly
> -----------------------------------------------
>
>                 Key: JBLOGGING-58
>                 URL: https://issues.jboss.org/browse/JBLOGGING-58
>             Project: JBoss Logging
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.0.0.Beta4-jboss-logging
>            Reporter: Dan Allen
>            Assignee: David Lloyd
>            Priority: Minor
>             Fix For: 3.0.0.CR1
>
>
> Currently, JBoss Logging uses a classloading approach to look for a logging provider based on a hardcoded order of precedence. While this is sufficient for the default case, there should be a way to specify the logger explicitly, in the case that there is more than one concrete logging implementation on the classpath.
> The override should be part of the API, though a system property could also be supported. The API would take precedence.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira