[slf4j-user] Using slf4j in a library project

[Jacob Kjome]

Though because LoggerFactory doesn't exist in slf4j-api.jar, this jar is kind of
useless, no?  Why is it built at all?  Only various implementation jars should
be built.

Jake

Quoting Franck Routier <franck.routier at axege.com>:

> Hi,
>
> you're right, you still depend on an implementation to run your app, but
> the beauty of the thing is you depend on _any_ implementation.
>
> So you let the choice to you users of what logging implementation they
> will choose.
>
> Does this make any sense ?
>
> Franck
>
>
> reg4000 at googlemail.com a écrit :
> > Hello,
> >
> > I have a question about the usage of slf4j in a library project. I
> > wonder how the library can depend on slf4j-api only.
> > As the slf4j-documentation suggest the standard usage pattern is
> >
> >  1: import org.slf4j.Logger;
> >  2: import org.slf4j.LoggerFactory;
> >  3:
> >  4: public class Wombat {
> >  5:
> >  6:   final Logger logger = LoggerFactory.getLogger(Wombat.class);
> >
> > The problem is that already this does not only depend on slf4j-api but
> > on some real implementation because of the missing of LoggerFactory in
> > slf4j-api.jar.
> >
> > Regards
> > ThoMo
> > _______________________________________________
> > user mailing list
> > user at slf4j.org
> > http://www.slf4j.org/mailman/listinfo/user
> >
> >
>
>
> _______________________________________________
> user mailing list
> user at slf4j.org
> http://www.slf4j.org/mailman/listinfo/user
>