This is an exported version of the JIRA issue tracker. Please use the Google Code site to open new tickets or report updates to these existing tickets. Feel free to contact the mailing list with any questions.

[SJN-31] Switch to Log4J
Created: Fri, 8 Aug 2003 23:36:05 -0700 (PDT)  Updated: Sun, 18 Jan 2004 17:18:50 -0800 (PST)

Status:Closed
Project:Simple-JNDI
Component/s:
Affects Version/s:0.6
Fix Version/s:0.8

Type:ImprovementPriority: Major
Reporter:Henri YandellAssignee:Henri Yandell
Resolution:Won't Fix 
Environment:


 Description   
There are lots of commented out debug statements. These need to sit on top of Log4j or java.util.logging.
Comment by bayard [ Fri, 21 Nov 2003 02:56:44 -0800 (PST) ]
It's really shit to look at and embaressing, so moving to log4j is moved up to 0.7.
Comment by bayard [ Sat, 6 Dec 2003 14:22:54 -0800 (PST) ]
Pushed back, no matter how embaressing.
Comment by bayard [ Sat, 6 Dec 2003 14:24:19 -0800 (PST) ]
This is because I'm undecided if I should bite the bullet and just use the JDK logging.
Comment by bayard [ Sun, 14 Dec 2003 20:27:58 -0800 (PST) ]
I've moved to the wonders of 1996 via a static-final DEBUG boolean and have improved the debug to not be quite as cryptic. Still deciding on a logging API to use, but will push this back again to a later version.
Comment by bayard [ Sun, 18 Jan 2004 17:18:50 -0800 (PST) ]
Deciding not to do this and declaring it closed for 0.8 where the DEBUG stuff was added.