[slf4j-dev] jcl-over-slf4j module not building

John E. Conlon jconlon at verticon.com
Fri Feb 16 21:38:48 CET 2007


Hi Sebastien,

I see what is going on, but don't know what to do about it.

The build problem is related to the introduction of a new package 
dependency to
the artifact (jar/bundle) created by jcl-over-slf4j.  This change 
happened at revision 722.

The new package dependency is

org.slf4j.spi

and it is used by the modified SLF4FLogFactory and the new SLF4JLocationAwareLog.  

To date we have considered the org.slf4j.spi a private package for use 
by the bindings projects only, it is never exported by any of our 
binding bundles and therefore was never intended to be used explicitly 
so it is never imported by any client bundles.  (OSGi bundles needing 
logging are only required to import the org.slf4j package. )

Even our own clients and jcl-over-slf4j is a client do not import this 
package and that is why the error during the maven package time. 

So how to get around the problem?  Revert to previous revision? But what 
about the fix for location specific logging?

John


Sebastien Pennec wrote:
> Hello,
>
> I've had some issues today by building the jcl-over-slf4j module. I get this error:
>
> [INFO] [bundle:bundle]
> [ERROR] Unresolved references to [org.slf4j.spi] by class(es) on the 
> Bundle-Classpath[Jar:dot]: [org/apache/commons/logging/impl/SLF4FLogFactory.class, 
> org/apache/commons/logging/impl/SLF4JLocationAwareLog.class]
>
> My guess is that it might come from OSGi wiring, but since I'm not too sure, I prefer 
> asking :)
>
> Sébastien
>   




More information about the slf4j-dev mailing list