> The issue was discussed in a somewhat abstract way durin july 2006 [1]. > > [1] http://www.slf4j.org/pipermail/dev/2006-July/000623.html > > Practically speaking, as a designer of a library you need to ship both > slf4j-api and an implementation say slf4j-simple.jar and let the end-user > replace the implementation if he or she decides to do so. Depending on your > distribution mechanism, allowing the user to replace the implementation > might be more or less difficult.
My confusion results mainly from the slf4j manual "Libraries Authors of widely-distributed components and libraries may code against the SLF4J interface in order to avoid imposing an logging API implementation on the end-user." (http://www.slf4j.org/manual.html) In a library you cannot only code against the SLF4J interface (aka api). Perhaps you can add a link to the discussion mentioned above. ThoMo _______________________________________________ user mailing list [email protected] http://www.slf4j.org/mailman/listinfo/user
