activemq-all, as its name suggests, bundles third-party dependencies in its
JAR (rather than declaring them as dependencies), and it happens to include
slf4j:
http://grepcode.com/snapshot/repo1.maven.org/maven2/org.apache.activemq/activemq-all/5.11.1
So I suppose, the first run finds slf4j classes
Hi!
Maybe I was too unclear about the specific problem.
I've got a project that has org.slf4j:slf4j-api:1.7.12 as dependency as it uses
the Logger in the Java code. The
dependency is declared in POM but comes also as a transitive dependency.
When running 'dependency:analyze' it is marked as
Maybe because
a) your project uses dependencies which were never declared explicitly
in any of your POMs and
b) at least some of your modules have dependencies declared which are
not actually used in your code?
What do you think?
--
Alexander Kriegisch
https://scrum-master.de
