Hi all,
at Syncope we embed ApacheDS in our build-tools, as support for integration 
tests.

I recently started noticing messages as follows, during startup:

SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in 
[jar:file:/home/ilgrosso/.m2/repository/org/apache/logging/log4j/log4j-slf4j-impl/2.11.1/log4j-slf4j-impl-2.11.1.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in 
[jar:file:/home/ilgrosso/.m2/repository/org/apache/directory/server/apacheds-service/2.0.0.AM25/apacheds-service-2.0.0.AM25.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.apache.logging.slf4j.Log4jLoggerFactory]

So I went checking the content of apacheds-service-2.0.0.AM25.jar as downloaded 
from Maven central, and found that it seems to embed its transitive 
dependencies (bouncy-castle, jdbm, slf4j, log4j2, ...): is there any rationale 
for this?
Would it be possible to get apacheds-service as plain JAR, so that dependencies 
can be managed within our Maven projects?

Thanks!
Regards.

Reply via email to