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

[ https://issues.jboss.org/browse/AS7-1389?page=com.atlassian.jira.plugin.s... ] Scott Hasse commented on AS7-1389: ---------------------------------- I understand JBoss might be more than just a JEE server, but when deploying a JEE application the basic container/application contract should be the JEE specification. Providing classloader visibility to a specific version of commons logging, log4j and slf4j by default causes problems for the hundreds of applications I work with. We've implemented isolated classloader repositories on previous EAP versions and still had to open over half a dozen support cases related to broken container isolation related to JBoss-provided logging implementations. Justifying this decision based on subjective philosophy and community feedback seems to put you down a slippery slope toward including everything and the kitchen sink. The spec seems like much firmer ground for JEE apps in particular. Do you still stand by this statement as well? Because it seems to me you've got it exactly backwards. Again, logging is not a JEE facility, so packaging your own is the portable approach. In my opinion a more correct default would be better than a simple way to change a bad default. Regards, Scott -- 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