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
