Given the time of year, I think everyone's focus will be elsewhere and starting vacations soon so I would rather just wait. I can't even do the minimal to use SLF4J Simple until that patch is reviewed and absorbed if it is accepted at all because. When I say inefficient it's on the order of breaking the performance test harness in SLF4J simple right now, so I'm sure my patch will not go in unchanged. I just wanted to prove it can work.
There is also the bit of work Hervé wants to do vis-a-vis isolating the SLF4J implementation and so that's going to take a few days anyway. On Dec 10, 2012, at 3:32 AM, Kristian Rosenvold <kristian.rosenv...@gmail.com> wrote: > As for options; there is also the option of accepting that the > technical challenges were slightly larger than anticipated and > that getting things right make take some more time. > > In this context we could push the slf4j introduction to a "3.1" branch > and release 3.0.5 now. Or just take the time. > > Kristian > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > Thanks, Jason ---------------------------------------------------------- Jason van Zyl Founder & CTO, Sonatype Founder, Apache Maven http://twitter.com/jvanzyl --------------------------------------------------------- You are never dedicated to something you have complete confidence in. No one is fanatically shouting that the sun is going to rise tomorrow. They know it is going to rise tomorrow. When people are fanatically dedicated to political or religious faiths or any other kind of dogmas or goals, it's always because these dogmas or goals are in doubt. -- Robert Pirzig, Zen and the Art of Motorcycle Maintenance
