Does sljf4j not use Service lookup to locate log implementations? Can
you please tell us how it discovers log implementations and why bundling
those two artifacts together affects the discovery process? Yes, we know
slf4j is in central repo, but we have a requirement in GlassFish project
to build external code in our own environment, hence we are promoting
our own binaries.
Sahoo
Ceki Gulcu wrote:
> Hello all,
>
>
> Just wanted to observe that combining slf4j-api and slf4j-jdk14 in a
> single module will prevent slf4j from being able to use any logging
> framework other that j.u.l. within Glassfish, which partially defeats
> the purpose of SLF4J as a logging abstraction. Is keeping the slf4j
> artifacts split an option?
>
> btw. 1.5.9.RC1 is already available in the central maven repository.
>
> Cheers,
>