I'm +1 for logback as the slf4j impl. /Anders
On Tue, Dec 11, 2012 at 3:32 AM, Jason van Zyl <ja...@tesla.io> wrote: > Hi, > > I looked around a bit more today and I don't think SLF4J Simple is viable > long term, I don't want to patch it anymore as I would have to do a day's > work to make changes that keep the performance levels up, get it reviewed > and released, and I honestly don't think it's worth it anymore. I would > rather spend my time building out the plugin test cases and help to finish > the classloader blocking of SLF4J. I don't mind spending time getting it > all working but I don't want to waste my time on an implementation we're > going to toss. > > After a conversation with the PMC it will require a vote to accept Logback > which is EPL but I wanted to ask committers and interested users about > using Logback. I believe Logback is the best choice as it's the most mature > and battle tested implementation because once it goes in it's likely not > ever to come out. Many of us are users and have integration experience with > Logback and it's what I use everyday for logging in all my other projects > and I've been a happy user for years. I see Logback as best of breed and > widely adopted including 8 projects at Apache. > > There's no point in asking the PMC to vote on the acceptance of Logback if > it's not acceptable by the community. If there are interested users I would > really like to hear what you think because you're the ones who will have to > live with the choice that is made. > > Thanks, > > Jason > > ---------------------------------------------------------- > Jason van Zyl > Founder & CTO, Sonatype > Founder, Apache Maven > http://twitter.com/jvanzyl > --------------------------------------------------------- > > To do two things at once is to do neither. > > -- Publilius Syrus, Roman slave, first century B.C. > > > > > >
