[ https://issues.apache.org/jira/browse/WICKET-711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gwyn Evans closed WICKET-711. ----------------------------- Resolution: Invalid Fix Version/s: 1.3.0-beta3 The 'main' code doesn't have the suggested dependancies on log4j - it's up to the user to choose which slf4j impl to use log4j, logback, simple-log or whatever they want - Wicket /doesn't/ mandate or even default to any. > Remove log4j dependency > ----------------------- > > Key: WICKET-711 > URL: https://issues.apache.org/jira/browse/WICKET-711 > Project: Wicket > Issue Type: Improvement > Components: wicket > Affects Versions: 1.3.0-beta1 > Reporter: Gili > Priority: Trivial > Fix For: 1.3.0-beta3 > > > Please consider removing Wicket's dependency on log4j. This can be achieved > quite easily by replacing slf-log4j*.jar by slf4j-simple*.jar. The > application footprint will shrink and all those ClassLoader problems log4j is > notorious for will go away: http://www.qos.ch/logging/classloader.jsp > Finally, I recommend you consider migrating to logback, which is a native > implementation of slf4j by the author of log4j: http://logback.qos.ch/ > It's logging performance and output format is above and beyond what log4j > provides. Once you try it you'll fall in love with the output format. Just my > 2 cents :) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.