About pom dependencies

Rod Widdowson rdw at steadingsoftware.com
Fri Sep 27 12:45:51 EDT 2013


I have started chasing up the IdP dependencies (using "mvn
dependency:analyze") This is a bit of a learning process, but is mostly
obvious I'll be writing a how-to wiki page on this in early October (my top
leaning tip so far is that just because mvn cannot see a dependency doesn't
mean you can just remove it).

Anyway, I did spot an oddity which I wanted to ask those who understand our
toolchain better than I.

Running dependency on idp-core throws up the need to depend on
'logback-core'.  What is odd about this (rather than say 'guava' or
'joda-time') is that the definition of this does *not* figure in the master
pom for java-parent-project.  Rather it specifies the exact version of
logback-classic, and the pom for logback classic specifies the dependency on
logback-core *but not specifying an exact version*.

My question is whether we should fix this by adding a logback-core and its
version into our master pom?

Rod



More information about the dev mailing list