[jboss-jira] [JBoss JIRA] (AS7-1389) Log API dependencies should be included automatically in deployments

[David Lloyd (JIRA)]

    [ https://issues.jboss.org/browse/AS7-1389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12934742#comment-12934742 ] 

David Lloyd commented on AS7-1389:
----------------------------------

JBoss AS and its successor, WildFly, are not Java EE containers, they are containers that happen to support Java EE (and have in the past and will in the future support other things as well, as the industry changes).  Given this, and that philosophy is subjective by definition, and community feedback over the years, I stand by this decision; I am sorry it does not hold up for your specific environment though.  To this end, there is another open task right now to add a management attribute which disables this behavior in the logging subsystem.  Since changing it will then be a simple matter, I think that would resolve this issue.
                
> 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