Since we use Resin, and Resin does support what you're describing, this is the approach I'm taking short-term.
In my resin setup when I run solr directly from apache-solr-1.2-dev.war, everything is great.
But for our embedded Jetty usage, I'll be back in the same situation as Ryan.
In a jetty+wicket environment that integrates with legacy log4j code, I'll try a Log4J LogManager -- thanks for the pointer Chris.
Not that I'm arguing for use of Apache Commons Logging (I've had enough fun with that in Nutch), just commenting on the discussion here.
I'm defiantly not promoting commons logging either! I also had less then great experience with it. I posted the question a few weeks back because both jetty and wicket use slf4j and i've had good luck with it so far. If solr also used it, _my_ stack would be consistent, but I understand I'm not running a typical setup and don't want/need to rock the boat if changes don't help anyone else... ryan
