[ https://jira.jboss.org/jira/browse/GTNPC-14?page=com.atlassian.jira.plugi... ] Thomas Heute updated GTNPC-14: ------------------------------ Fix Version/s: 2.1.0-CR02 (was: 2.1.0-CR01) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/GTNPC-14?page=com.atlassian.jira.plugi... ] Chen Wang commented on GTNPC-14: -------------------------------- It would be extremely helpful if the dependency on log4j can be removed and replaced with a logging wrapper such as gatein logging or even jboss common logging. It would probably open the possibility of removing log4j jar from Tomcat's lib dir which has already caused us classloading problem when deploying our in-house portlets. I've tried replacing log4j through slf4j with jdk14 logging but portlet container cannot start because of the hard dependency. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/GTNPC-14?page=com.atlassian.jira.plugi... ] Julien Viet resolved GTNPC-14. ------------------------------ Resolution: Done -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira