[ https://issues.jboss.org/browse/AS7-1389?page=com.atlassian.jira.plugin.s... ] David Lloyd commented on AS7-1389: ---------------------------------- 99% of the time I think the user wants to have centrally configured logging, in which case the deployment should use our APIs and just ignore whatever is packaged with the application whether it was included intentionally or not. As it is right now if people include logging JARs it's hard to say exactly what will happen - sometimes nothing is logged (for example if the slf4j API is bundled with no impl and the no-op logger is selected), sometimes the app will have separate logging (if it uses log4j and they bundle their own), sometimes it will use container logging (if they do not bundle anything, or if they include their own slf4j API but use Dependency: or another mechanism to get our impl). I'd rather require that users include the JARs *and* specify the dependency exclusion if they want to do their own logging outside of the container. Otherwise all logging should always go through the container just for consistency if nothing else. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-1389?page=com.atlassian.jira.plugin.s... ] Jason Greene updated AS7-1389: ------------------------------ Fix Version/s: 7.1.0.Beta1 (was: 7.1.0.Alpha1) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-1389?page=com.atlassian.jira.plugin.s... ] Jason Greene updated AS7-1389: ------------------------------ Fix Version/s: 7.1.0.CR1 (was: 7.1.0.Beta1) Moving all non-critical issues to the CR. If you finish it before we release beta please correct the fix-for version. Thanks -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-1389?page=com.atlassian.jira.plugin.s... ] Lars Fischer commented on AS7-1389: ----------------------------------- -1 The need to exclude not wanted dependencies breaks portability of deployable items. If there are logging jars included and they worked on other servers, then it should also work on jboss without a need to repackaging/reconfiguring all. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-1389?page=com.atlassian.jira.plugin.s... ] Lars Fischer commented on AS7-1389: ----------------------------------- {quote} If a user does include such JARs they would be ignored, thus the deployment will continue to work. If the user explicitly wants to use their own logging JARs for some reason, then they'd configure the exclusion. {quote} Is this the current behaviour or your suggestion? Ignoring included jars is NOT what I define as working, because expected functions (the defined logging) are disabled or behaving different. One goal of JEE6 was to increase portability of applications (e.g. through portable JNDI paths). Introducing another need to touch applications to enable expected behaviour on different AppServers is a step back. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira