[
https://issues.jboss.org/browse/AS7-1389?page=com.atlassian.jira.plugin.s...
]
Scott Hasse commented on AS7-1389:
----------------------------------
The decision to include visibility to specific third party logging implementations by
default seems absolutely against the basic philosophy of modules in a JEE container
environment. This sort of logging is simply not a JEE container feature and default
visibility should not be provided and the debate should end there. Those wanting to use
the vendor-specific non-spec container facility should be the ones configuring an explicit
dependency.
I find David Lloyd's anecdotal observations on which this decision was based to be
simply not accurate in my large enterprise experience where you want to decouple the
application from the container excepting for the specified JEE facilities. If someone
thinks otherwise I'm certainly interested to understand why.
Especially justifying the decision based on portability seems exactly backwards. JBoss is
going beyond the specification to provide a vendor-specific facility that in fact reduces
portability.
Please consider re-thinking this decision moving forward.
Scott
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
Assignee: James Perkins
Fix For: 7.1.0.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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira