Actually thinking for alternatives rather than just shooting it down
because it might not fit one's mental model is what I appreciate
most.
"I don't want to try it", without alternatives or thinking through
other options is what I found very frustrating and fueled much of my
persistence.
I find it somewhat offensive that you think anyone's opinion on this
list is just "I don't want to try it", as if they haven't thought
through other options and made a value decision on what the best
solution here is. This isn't just "trying something" - this is making
a decision about how logging works in JSecurity.
There have been many compelling arguments as to why we should use
SLF4J vs a proprietary logging abstraction layer. I don't think
anyone is arguing for one side or the other here without taking these
arguments into account.
The idea of bundling in the SLF4J API has been mentioned many previous
times. I'm fine with creating a normal jar and a normal jar + slf4j
api bundled in. This makes it easy to just include the uber jar in
projects that don't want to manually include SLF4J.
I haven't heard any arguments for why including SLF4J wouldn't work or
poses a real problem that are compelling to me.
Jeremy
