Did you finally tried "full graph analysis on Central to see what Maven plugins actually depend on SLF4J or an implementation" as intended on february 1st? This was a great idea to have some facts to predict problems like SONAR-3979
But if such idea is harder than expected, doing a release and seeing bug reports is better than waiting, I have no big problem. And personnally, I gave up on implementing slf4j isolation: that's a Maven internal I can't understand yet. So, ok for me for the release plan Regards, Hervé Le mardi 26 février 2013 09:05:36 Jason van Zyl a écrit : > As I posted previously I would like to do the 3.1.0 release but I don't want > to do the work of isolating SLF4J until it's shown that it will be a > problem. I don't the believe the adoption of 3.1.0 is going to be so quick > that we can't create a fix if necessary. I would rather do the release in a > lean style and not do work for theoretical problems. > > In full disclosure I have a release of Tesla I want to make and I already > have JSR330, SLF4J/Logback, and Eclipse Aether integrated so I would like > to try and help get the JSR330, SLF4J out the door and then get Eclipse > Aether integrated. > > If anyone feels strongly about trying to create the SLF4J isolation and is > going to start the work to do it shortly there's no harm in waiting. But I > would prefer to start getting the 3.1.0 release out the door, get some > feedback and adjust if necessary. > > Thanks, > > Jason > > ---------------------------------------------------------- > Jason van Zyl > Founder & CTO, Sonatype > Founder, Apache Maven > http://twitter.com/jvanzyl > --------------------------------------------------------- > > Simplex sigillum veri. (Simplicity is the seal of truth.)
