Open GoogleCodeExporter opened 9 years ago
Original comment by bantc...@gmail.com
on 30 Mar 2011 at 10:01
Original comment by bantc...@gmail.com
on 31 Mar 2011 at 2:42
Original comment by bantc...@gmail.com
on 31 Mar 2011 at 2:46
Replace logger mechanism by using eg. java.util.Logger
Original comment by bantc...@gmail.com
on 31 Mar 2011 at 2:59
[deleted comment]
[deleted comment]
I'd suggest using the Simple Logging Facade for Java (SLF4J)
http://www.slf4j.org/
This way the logging is completely indepentend of the log implementation.
Original comment by reg.goog...@future-invent.de
on 31 Mar 2011 at 4:22
Sounds good!
Original comment by bantc...@gmail.com
on 31 Mar 2011 at 5:06
slf4j is useful for a library that must be integrated in heterogeneous
environments. For a small standalone application like Keytool IUI the standard
logging package in java.util.logging is good enough.
Original comment by ebo...@apache.org
on 5 Apr 2011 at 10:34
As for info, I am using java.util.Logging in a project named geoForge.
It uses a small mechanism to redirect log messages into the right file location.
wiki page:
http://code.google.com/p/geoforge/wiki/developmentLoggerMechanism
Original comment by bantc...@gmail.com
on 6 Apr 2011 at 3:24
Original comment by bantc...@gmail.com
on 5 Jun 2011 at 8:28
I'll handle this one.
Original comment by bantc...@gmail.com
on 4 Sep 2011 at 2:06
Original issue reported on code.google.com by
bantc...@gmail.com
on 30 Mar 2011 at 9:59