We partly use slf4j internally already for tests, etc. But moving the whole Logger mess over to slf4j would be really great. There are lots of tests (I sadly also found productive code too) still using System.out.println.
The question is if we (internally) drop org.codehaus.plexus.logging.Logger completely and use slf4j directly, or if we pimp up the plexus Logger and add various stuff. We would need to do some compat code anyway, but I'm not sure if it pays off to restrict ourself. At least not after I saw that even the LoggerManager uses System.err.println: // TODO: use a logger! System.err.println( "There was no such logger '" + key + "' " + hashCode() + "." ); dumdidum :) LieGrue, strub --- On Fri, 6/10/11, Ralph Goers <ralph.go...@dslextreme.com> wrote: > From: Ralph Goers <ralph.go...@dslextreme.com> > Subject: Re: Get thee to the Core... > To: "Maven Developers List" <dev@maven.apache.org> > Date: Friday, June 10, 2011, 5:03 AM > > On Jun 9, 2011, at 2:45 PM, Benson Margulies wrote: > > > I'd like to offer a small suggestion. > > > > One of the big barriers to maven happiness is the > difficulty of > > understanding, in some cases, why it does what it > does. > > > > This suggests to me three efforts that might offer an > opportunity to > > learn core code without drowning. > > > > 1: take up slf4j, and thus allow component (indeed > class) by component > > log control as an alternative to the giant -X spew. > > Now that is an interesting idea. For the past year I have > been working on creating Log4j 2.0 pretty much by > myself. This would be a great way to integrate it into > something useful. > > Ralph > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
