[
https://issues.jboss.org/browse/AS7-1389?page=com.atlassian.jira.plugin.s...
]
David Lloyd commented on AS7-1389:
----------------------------------
99% of the time I think the user wants to have centrally configured logging, in which case
the deployment should use our APIs and just ignore whatever is packaged with the
application whether it was included intentionally or not. As it is right now if people
include logging JARs it's hard to say exactly what will happen - sometimes nothing is
logged (for example if the slf4j API is bundled with no impl and the no-op logger is
selected), sometimes the app will have separate logging (if it uses log4j and they bundle
their own), sometimes it will use container logging (if they do not bundle anything, or if
they include their own slf4j API but use Dependency: or another mechanism to get our
impl).
I'd rather require that users include the JARs *and* specify the dependency exclusion
if they want to do their own logging outside of the container. Otherwise all logging
should always go through the container just for consistency if nothing else.
Log API dependencies should be included automatically in deployments
--------------------------------------------------------------------
Key: AS7-1389
URL:
https://issues.jboss.org/browse/AS7-1389
Project: Application Server 7
Issue Type: Bug
Components: Logging
Affects Versions: 7.0.0.Final
Reporter: David Lloyd
Fix For: 7.0.1.Final
The following log APIs should be included by deployments by default:
* {{org.slf4j}}
* {{org.apache.commons.logging}}
* {{org.log4j}}
These dependencies should override the deployment's versions of these libraries
unless explicitly excluded by {{jboss-deployment-structure.xml}}.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira