Adam,
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?
Gump has proved itself by catching the problem. We may be able to fool gump but the problem is going to surface at runtime, unless of course it gets fixed before.
Yes, the best action is to fix it, not to hide from it.
How about removing the workaround for gump so that commons-logging explicitly won't build, thus raising the schedule pressure for whoever looks after commons-logging?
-Steve
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
