Although I'm used to log4j, I'd much prefer learning commons-logging to 1.4 since I don't think we should be JDK 1.4 dependant. My project is still in the dark ages of JDK 1.3.1, so this wouldn't work for me anyway. I'm sure there are other users with this same requirement.
+1 commons-logging On Sat, 29 Mar 2003, Matt Raible wrote: > I agree that we should: > > 1) get rid of explicit paths in local.properties and add servlet.jar to > CVS. > > 2) go for commons-logging vs. log4j. I'd rather use commons-logging > than ln2 b/c > > <fear of learning another API> > I think more folks are familiar with it and it represents a more common > approach in open source tools. > </fear of learning another API> > > Matt > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On > > Behalf Of Joseph Ottinger > > Sent: Saturday, March 29, 2003 5:55 AM > > To: [EMAIL PROTECTED] > > Subject: [displaytag-devel] Build oddities > > > > > > I did a new checkout of the displaytags stuff this morning in > > order to correct Neal's problem with incidental use of the > > 1.4 API... and the local.properties is a little odd. > > > > For one thing, ant has a built-in classpath; why are we using > > explicit references to jars when simply including all files > > in ./lib would do the same thing? (IMHO, servlet.jar should > > be included in the CVS tree, if only to make it a "check out > > and build" process.) > > > > <bias> > > Likewise... reliance on log4j for logging is a little severe > > (again, IMHO). For one thing, log4j is 160K of "maybe we want > > it." Yuck. Also, log4j use is becoming less popular in the > > face of two other things: 1.4's built-in logging and > > Jakarta's commons-logging, which is a front end for log4j and > > the 1.4 logging (and doesn't require either). commons-logging > > is also MUCH, MUCH smaller than log4j. In addition to that, I > > have my OWN logging project, smaller than commons-logging > > (21K), that is an n-space logger instead of a hierarchical > > logger (and includes a mechanism by which you can trace > > method calls made into a given class, if you like, without > > having explicit logging calls.) > > > > I'm biased, obviously. I'm not changing any of this; I just > > wanted to run it by you. My logger is at > http://enigmastation.com/ln2, if you're interested... which reminds me, > I need to update the web site to cover recently-added features. :) > </bias> > > --------------------------------------------------------- > Joseph B. Ottinger [EMAIL PROTECTED] > http://enigmastation.com IT Consultant > > > > ------------------------------------------------------- > This SF.net email is sponsored by: > The Definitive IT and Networking Event. Be There! > NetWorld+Interop Las Vegas 2003 -- Register today! > http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en > _______________________________________________ > displaytag-devel mailing list [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/displaytag-devel > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: > The Definitive IT and Networking Event. Be There! > NetWorld+Interop Las Vegas 2003 -- Register today! > http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en > _______________________________________________ > displaytag-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/displaytag-devel > -- John York Software Engineer CareerSite Corporation ------------------------------------------------------- This SF.net email is sponsored by: The Definitive IT and Networking Event. Be There! NetWorld+Interop Las Vegas 2003 -- Register today! http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en _______________________________________________ displaytag-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/displaytag-devel
