[logback-user] Need for a simple packaging structure for logback. A single jar file would be great!

rathnadhar.kolar at wipro.com rathnadhar.kolar at wipro.com
Wed Mar 9 03:42:38 CET 2011


I have been using logback for some time now. I find it very good.
Earlier I was using log4j. 

I have one comment on logback:

Currently I find the packing of logback very confusing. There are too
many jar files for me to track (say logback : access, classic, core) ,
then I have to deal with plethora of jars in slf4j (simple, nop, etc). 

While these packages may have evolved over time to give flexibility to
the logging solution. I find it very hard to keep track of what is
required when. I get binging exceptions from the resulting confusion.

My suggestion is it would be really great if there is only one
logback.jar that has all the functionality to meet the basic logging
needs such as logging to console, rolling file, smtp. This will help to
resolve the complexities of the jar in logback solution.


"Aham Brahmasmi" Brhadaranyaka Upanishad 1.4.10

Please do not print this email unless it is absolutely necessary. 

The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. 


More information about the Logback-user mailing list