I tried SLF4J for a project and found it better than commons as well. The pain is that maven has a lot of dependencies with commons logging and it is a little hard to remove. Apparently 1.1.1 is supposed to have a better pom file.
On Fri, Apr 25, 2008 at 8:04 AM, Manfred Geiler <[EMAIL PROTECTED]> wrote: > +1 for removing any (transient) dependency to commons-logging > > And for logging that myfaces-commons-util classes wanna do themselves > I strongly suggest SLF4J! > > --Manfred > > > > > On Thu, Apr 24, 2008 at 8:16 PM, Scott O'Bryan <[EMAIL PROTECTED]> wrote: > > Hey guys, > > > > At the risk of getting hit with tomatoes and all kinds of rotten fruit, I > > would like to ask about some of the dependencies for the MyFaces Commons > > projects. IMO the MyFaces commons projects should not carry around an > > unnecessary amount of dependencies. "Provided" dependencies are one thing, > > but in general I think that dependencies on the JSF and Servlet should be > > just about the extent of it for most libraries. > > > > Currently the myfaces-commons-util's has a runtime dependency on the > Apache > > Commons Logger. This means that if I'm using the renderkit and the R.I. I > > have to also include the logger in my libraries. I would like to remove > > this dependency and either use J2EE logging or standard java logging. > > Better yet, we might be able to beef up the contract on the utilities to > > throw exceptions and let logging be handled by the parent application. > > > > Does anyone concur? If not, please don't throw any tomatoes at me. :) > > > > Scott > > > > > > -- > http://www.irian.at > Your JSF powerhouse - JSF Consulting, > Development and Courses in English and > German > > Professional Support for Apache MyFaces >
