Hi,
> I wholeheartedly agree. Dropping 1.2 support "just because it's old" is > very silly - there must be some -reason- behind that choice. > > Regards, > Endre True, but the reason doesn't have to be technical. If, for a given log4j release, the marginal cost (in terms of developer time spent on the issue, for example) of maintaining JDK 1.2 support exceeds the marginal benefit (in terms of how many users of that release use JDK 1.2 AND would update to the given log4j release), that's a reason to dump support. That's fairly elementary project management. Of course, if there's a developer willing to spend all the time and effort needed to support it, so be it. Until we actually run into a technical reason. On a related note, the adoption rate (migration from older versions to latest) for Tomcat 5.5 is higher than for previous branches, even though we made a decision to design for J2SE 5.0, and allow running on JDK 1.4 as well, but not even JDK 1.3, much less 1.2. We thought it might slow down adoption or generate complaints, and the opposite has been true. I'm not saying log4j is the same type of product, just providing a data point. Yoav
BEGIN:VCARD VERSION:2.1 N:Shapira;Yoav FN:[EMAIL PROTECTED] ORG:MIT Sloan School of Management TITLE:System Design and Management Fellow URL;WORK:http://www.yoavshapira.com EMAIL;PREF;INTERNET:[EMAIL PROTECTED] REV:20050611T145830Z END:VCARD
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
