On 17 May 2004, at 17:20, Adam R. B. Jack wrote:
Given that you have supplied a corrective patch 5 days ago, and that no commons-logging developer has picked it up, do you think pretending the problem does not exist is the wisest approach?
It isn't quite that simple, although your comments make me smile. ;-)
Gump isn't just a build script, it is that plus the effects/outcomes of
communities trying to get/stay aligned. We can't expect folks to drop what
they are doing the second something comes up, it just doesn't work that way
in the OSS world. Much as I might think that the C-L folks ought find it
easy to apply the patch (and perhaps should have done the fix a year plus
ago) I am not aware of the factors impacting that project, nor do I wish to
judge.
<sigh>
if the upcoming commons-logging release contained this patch then the impact on all those downstream projects would be huge. log4j CVS HEAD is no longer binary compatible with the last release version. everyone using the existing release of log4j with the next commons-logging release (which is coming soon) would find that their logging was broken.
i'm not willing to apply a patch that makes common-logging incompatible with the last released version of log4j. i'd also be willing to veto any one who commits such a change. there are other ways around this issue but it's going to take a little time.
i make no apologies for putting the needs of the downstream users of commons-logging higher than the need to fix this problem hastily. i have been looking into this tonight and i've posted a proposal solution to the mailing list. if no one can find a hole in it, i'll probably have something in place tomorrow.
- robert
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
