+1 ### Random auto-corrects and typos are my special gift to you. When I forward they are from others.
> On Mar 3, 2015, at 10:03 AM, Henry Saputra <[email protected]> wrote: > > Sounds like good suggestion to me. > > > - Henry > >> On Tue, Mar 3, 2015 at 9:55 AM, Keith Turner <[email protected]> wrote: >> Why does twill have compile time bindings on logback? Is there a way to >> avoid this, can I use twill to launch something that uses log4j? If not, >> would it make sense to move twill logback code to an optional twill >> module/jar? >> >> The following is taken from http://www.slf4j.org/codes.html >> >> Embedded components such as libraries or frameworks should not declare a >> dependency on any SLF4J binding but only depend on slf4j-api. When a >> library >> declares a compile-time dependency on a SLF4J binding, it imposes that >> binding >> on the end-user, thus negating SLF4J's purpose. When you come across an >> embedded component declaring a compile-time dependency on any SLF4J >> binding, >> please take the time to contact the authors of said component/library and >> kindly ask them to mend their ways. >> >> Thanks >> >> Keith
