On Feb 26, 2005, at 5:25 PM, Jacob Kjome wrote:
Curt, I understand your wanting to keep compatibility. I tend to agree that if we can do it at the same time as adding new features, then we should strive for that. We broke compatibility with RepositorySelector's, but because there are few (if any besides the log4j-sandbox, which are now removed) outside implementations and it added real value to Log4j-1.3, it made sense.
I agreed with that decision. It did break the Gump build of Jetty since they had implemented their own repository selector. There seemed to be no reasonably simple way to maintain backward compatibility and it would have been fairly simple for them to modify their code to work with both log4j 1.2 and 1.3. However, since that project was dormant (after being consumed into an Apache project, I believe), their Gump descriptor was modified to point to log4j 1.2.
I did a quick scan of Gump descriptors and the projects are configured to build against log4j 1.2:
excaliber-logging : switched 1/15/2005 due to API change in DOMConfigurator.doConfigure.
eyebrowse: switched 10/11/2004, no mention in their dev mailing list
jakarta-turbine-fulcrum: switched 2/11/2005, Must have same logger as excaliber-logger
jakarta-velocity: switched 12/01/2004, appears to be due to the change of o.a.l.RollingFileAppender to o.a.l.rolling.RollingFileAppender
http://mail-archives.apache.org/eyebrowse/ReadMsg?listName=velocity- [EMAIL PROTECTED]&msgNo=11427
james-server: log4j-1.2 dependency added 10/17/2004. No mention of the motivation for choosing to build against 1.2 instead of CVS HEAD.
None of these projects appear to be dormant. They represent about 5% of the Gump projects which I think is a surprisingly high loss for a dot release among our friends. If 5% of closed-source projects that use log4j have similar issues, we are going a pretty constant stream of frustrated corporate developers once 1.3 approaches release.
I don't know if this is reliable, but http://brutus.apache.org/gump/public/gump_stats/module_dependees.html indicates that more Gump projects depend on logging-log4j-12 (450) than logging-log4j (384). I guess due primarily to velocity and excalibur's dependence on log4j 1.2.
Hopefully as we move towards 1.3, we can bring some of these back into the fold where they work with both 1.2.x and 1.3. However, I think we should avoid making major projects like Velocity choose between 1.2 and 1.3 if we can help it.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
