[
https://issues.apache.org/jira/browse/WICKET-711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509102
]
Johan Compagner commented on WICKET-711:
----------------------------------------
what does it matter what examples uses?
performance of the logger? why would that be importand for a example project?
i am perfectly fine with Log4J in our examples. But if somebody wants to see
something different they can patch and configure it for us.
> 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
>
> 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.
