From: SourceForge.net <no...@so...> - 2005-10-09 16:24:52
|
Bugs item #1286854, was opened at 2005-09-11 01:03 Message generated for change (Comment added) made by arianne_rpg You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101111&aid=1286854&group_id=1111 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed Resolution: None Priority: 1 Submitted By: Miguel Angel Blanch Lardin (arianne_rpg) >Assigned to: Miguel Angel Blanch Lardin (arianne_rpg) Summary: Stendhal: Client using log4j Initial Comment: I don't think it is a good idea to make client use log4j mainly because it is a 3MB download that is in most cases completly ignored. Anyway, we can live with it until the release time. ---------------------------------------------------------------------- Comment By: Miguel Angel Blanch Lardin (arianne_rpg) Date: 2005-10-09 18:24 Message: Logged In: YES user_id=3949 Thanks you for your time on submitting this bug! Please checkout the new CVS, this bug has been fixed. If you are not satisfied with the solution, please reopen the bug. ---------------------------------------------------------------------- Comment By: Miguel Angel Blanch Lardin (arianne_rpg) Date: 2005-09-12 23:56 Message: Logged In: YES user_id=3949 Yeah, that seems a good solution. ---------------------------------------------------------------------- Comment By: Matthias Totz (mtotz) Date: 2005-09-12 22:42 Message: Logged In: YES user_id=1127086 I don't want to kick Log4J completly (for development it is crucial). So maybe invent a wrapper Logger class which loads Log4J- Logger when the jar is on the classpath, else it simply returns a dummy logger. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101111&aid=1286854&group_id=1111 |