[logback-user] Jetty conflict
rgoers at apache.org
Thu Feb 4 01:43:16 CET 2010
If you think about it, this is one area where all the app servers seem to really suck. Having them in your war means your application can control the version and if you want to upgrade the process is really simple. If you have multiple web applications in the server each can be independently using their own stuff. Relying on the jars in the classpath can make it risky to upgrade them and might possibly break the app server.
Ideally, the only thing that should be on the classpath that the application sees is the API that the app server provides. Everything else should be invisible behind a different classloader. Of course, if it was easy to do they would all be doing it that way.
On Feb 3, 2010, at 10:56 AM, Nikolas Everett wrote:
> Why not remove slf4j and logback from your war?
> Logback-user mailing list
> Logback-user at qos.ch
More information about the Logback-user