[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: ---------------------------------- With respect to point 4), you have said "I'm not sure #4 is really so black and white". Again I find myself in confused disagreement. It seems to be quite clear from my perspective that the implementation as-is reduces portability. I don't think there is any debate that log4, slf4j and commons logging are not a part of the JEE spec or Java platform. I'm also not aware of any other JEE container vendor that provides a container logging facility that ignores application-packaged implementations and configurations (and as you have pointed out "Unlike other containers we actually provide users with slf4j, commons-logging, log4j, and (working) JUL APIs..."), so it seems this facility is very vendor-specific. I asked above how you would categorize visibility to log4j, etc. It seems to me the most appropriate categorization in the context of the JEE specification is as a platform or product "extension". These are certainly allowed, for instance per JEE 7 spec section EE.2.10 ("A Java EE product may provide additional Java APIs..."). However that section also states "Of course, portable applications will not make use of any platform extensions. Applications that do make use of facilities not required by this specification will be less portable." So it seems very clear to me that using a vendor-specific platform extension is less portable. Again, if I am misunderstanding or misrepresenting something I would appreciate being corrected. Bullet-point-wise I'm almost past the half-way point of trying to better understand your perspective and find myself basically as confused and ignorant of it as when I started. 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