On Wed, Nov 10, 2010 at 3:48 PM, Todd Lipcon <[email protected]> wrote:
> Tom has discovered that bumping the log4j version to 1.2.16 instead of > 1.2.15 fixes the issue... > > should we just do that? I think that sounds reasonable. -- Owen
On Wed, Nov 10, 2010 at 3:48 PM, Todd Lipcon <[email protected]> wrote:
> Tom has discovered that bumping the log4j version to 1.2.16 instead of > 1.2.15 fixes the issue... > > should we just do that? I think that sounds reasonable. -- Owen