[
https://issues.jboss.org/browse/AS7-1389?page=com.atlassian.jira.plugin.s...
]
David Lloyd commented on AS7-1389:
----------------------------------
Scott, I'm not going to argue about it. You seem to feel bitter about it and you
apparently believe that your viewpoint is "common sense" and thus there's no
way to pursue the discussion rationally beyond what was already said.
I can tell you that if you're curious about what APIs are visible from a deployment,
you can examine (in JConsole) the JBoss Modules MBean corresponding to the service module
loader, and find a deployment module and look at its dependencies. That may give you an
idea of what facilities are available to applications.
As for the change not being in EAP - assuming that the proper RFE process is followed, it
is not unreasonable to expect this change to be backported, same as any requested feature
or enhancement.
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