You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Gwyn Evans (JIRA)" <ji...@apache.org> on 2007/06/29 10:27:04 UTC
[jira] Commented: (WICKET-711) Remove log4j dependency
[ https://issues.apache.org/jira/browse/WICKET-711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509052 ]
Gwyn Evans commented on WICKET-711:
-----------------------------------
As far as I can see, Wicket builds with slf4j-api and it's up to the user to choose the implemtantion they want at run-time, so *what* dependency on log4j? File/line details?
Left open (for the moment) in case I'm missing, something.
/Gwyn
> 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.