[
https://issues.jboss.org/browse/AS7-1389?page=com.atlassian.jira.plugin.s...
]
Scott Hasse commented on AS7-1389:
----------------------------------
Concerning point 7, I will say I am glad that a simpler configuration mechanism is being
implemented, and a support customer I work with has made a request to back-port that
change to EAP 6, so hopefully we can avoid adding additional configuration to applications
migrating to EAP 6 that will ultimately be extraneous anyway.
However, when talking about a strategic decision in a future version of the platform, I
don't think the relative ease of enabling/disabling a feature should be a strong
consideration. Rather, I think the a choice should be made on the merits of the
feature/facility as it stands.
Regards,
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