hi, I had similar problem. I think jetty doesn't find the file for configuration, and so uses the defaults which are a bit verbose. You may take a look here, to see what I did to avoid that https://github.com/oolekk/liftrulez.com/blob/master/src/main/scala/bootstrap/liftweb/Start.scala The point is, you need to set up logback very early. BTW this is a toy project, so don't expect too much from it, but this part dealing with logback actually worked. I think this should be same/similar with slf4j
On 13/11/12 21:01, Marty Sullivan wrote:
Hello, I added another dependency to my project that uses Jetty and, in turn, the slf4j.jar was also added to my project. Since then, Jetty is filling up my console as it seems to be set to DEBUG. How do I change the level to INFO or WARN for this logger? org.eclipse.jetty.util.log.Slf4jLog is the culprit. _______________________________________________ jetty-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/jetty-users
_______________________________________________ jetty-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/jetty-users
