That may meet the functional need but (a) it's unacceptable to the Solr dev's for the same reason that ANYTHING other than JUL is on principle, and (b) even someone like me finds the notion of a project specific log manager of sorts too be worse on principle than any other possible choice (JUL or SLF4J). I have principles too, and that's exceeds my threshold.
As an aside, I do wonder why there isn't a JUL to Log4j adapter out there... maybe our energies would be better served directed at such a thing. ~ David Henrib wrote: > > > > ryantxu wrote: >> >> As long as there is strong opposition, I think we can deal with JUL... >> > > We can; an attempt to mitigate JUL & the functional need is > https://issues.apache.org/jira/browse/SOLR-549 SOLR-549 . > It does respect the JUL choice and is a practical compromise that noone > seems to seek... > > -- View this message in context: http://www.nabble.com/Solr-Logging-tp16836646p16982528.html Sent from the Solr - Dev mailing list archive at Nabble.com.
