On Mon, May 24, 2010 at 05:11, tony mancill <[email protected]> wrote: > I'm not sure what your minimal test case is meant to exhibit. The warnings > you're seeing from log4j are normal warnings you see when there isn't a > log4j.properties file. That is, log4j is simply letting us know that a > component attempted to use it but that there were no appenders configured. If > you add have a valid log4j.properties file available on the classpath (sample > attached), you'll see what JPF is attempting to log. > > As for why this warning would appear after an upgrade to osmosis, my initial > guess would be that previous versions had a valid log4j configuration > available, > and that this is no longer the case. Or, it could be that the jpf.properties > file is missing or as moved (and so JPF can't find its configuration). I'll > experiment with osmosis this week as time allows.
Right, this bug is merely meant to note that previously I didn't have to know or care about log4j when installing osmosis, but after an upgrade all my cron jobs started to output the log4j lines. Forcing me to either learn how to silence it, or just grep the problem away. It would be nice if the default osmosis was set up so that it came with log4j settings that made it as verbose as it was before. But I have no idea if that makes sense, maybe this should be a wontfix. Thanks for looking at the issue. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
