I think that the main problem is that the author of the software which uses log4j is often not in control of either the other software with which it might be used or the version of log4j that is used.
Anders Kristensen wrote: > > Well, you always have the option of not upgrading to newer versions of > log4j. It sounds like that's the strategy you've chosen for JDBC > drivers. Then what you need is a assurance that the old version you're > using will continue to be maintained and have bugs fixed etc. That's a > very different thing and one for which it will probably be easier to get > a "guarantee". > -- This message may contain confidential information and will be protected by copyright. If this email isn't for you then we'd be grateful if you could notify Volantis by return and delete it. You should not copy, disclose or distribute any of its contents. Any reply may be read by the recipient to whom you send it and others within Volantis Systems Ltd. Although we aim to use efficient virus checking procedures we accept no liability for viruses and recipients should use their own virus checking procedures. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
