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
