By 'stops all logging', I mean any of my custom logging in my bundle classes that uses slf4j stops producing log output.
I think the problem must be related to this: http://stackoverflow.com/questions/11786265/multiple-slf4j-bindings-error-with-activemq-all-5-6-0-jar activemq-all brings in a lot: http://mvnrepository.com/artifact/org.apache.activemq/activemq-all/5.8.0 I think I'll instead try to just use activemq-core and try to figure out its missing dependencies, since all I want to do is produce and consume messages, not run an embedded broker. For your question 'Do you embedd activemq in the bundle ?', is there something else I could do? yes, the scope is compile (or at least the default maven scope). I tried using 'exclusions' but it doesn't seem to work, and I found this information: http://stackoverflow.com/questions/11786265/multiple-slf4j-bindings-error-with-activemq-all-5-6-0-jar "Unfortunately because they used the shade plugin you can not use exclusions in your activemq-all dependency definition in your POM." "The ActiveMQ guys use the Maven Shade Plugin to create the activemq-all "ueber" jar. Somewhere between version 5.5.1 and 5.6.0 they added the org.slf4j:slf4j-log4j12 dependency - hence your problem." Rob On Mar 19, 2013, at 8:58 AM, Felix Meschberger wrote: > Hi Rob > > I am a bit confused: What do you mean by "stops all logging" ? And what does > it have to do with a bundle's dependency ? > > Can you build and deploy the bundle at all ? Can the bundle be > resolved/activated ? > > Do you embedd activemq in the bundle ? What about transitive dependencies > (you have a compile scope dependency to activemq which generally drags in > transitivies dependencies ...) ? > > Regards > Felix > > Am 19.03.2013 um 08:53 schrieb Robert A. Decker: > >> Hello, >> >> The following dependency stops all logging in one of my bundles: >> <dependency> >> <groupId>org.apache.activemq</groupId> >> <artifactId>activemq-all</artifactId> >> <version>5.8.0</version> >> </dependency> >> >> But when I instead include this dependency logging is fine in the bundle: >> <dependency> >> <groupId>org.apache.activemq</groupId> >> <artifactId>activemq-core</artifactId> >> <version>5.7.0</version> >> </dependency> >> >> (unfortunately activemq-core is missing some dependencies) >> >> I have another bundle that isn't logging either but I don't know what >> dependency is interfering with it. >> >> How do I find what's stopping the logging, and is there a way around it? >> >> Rob > > > -- > Felix Meschberger | Principal Scientist | Adobe > > > > > > > >
