Suppose your project depends on class Foo from project p1 (and so declares a compile-scope dependency on p1).
But class Foo extends class Base from project p2 (and so p1 has a compile-scope dependency on p2). So project p2 (even though it is a transitive dependency) is needed at compile time for your code. P2's runtime dependencies will not be needed, so I suppose those are not fetched. http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html Cheers, Simon ---- Nick Stolwijk <[EMAIL PROTECTED]> schrieb: > Then I was wrong there. I thought when maven needs a dependency for > compilation, it wouldn't need the transitive dependencies. > > With regards, > > Nick Stolwijk > > Simon Kitching wrote: > > Nick: for maven2, if a pom declares a dependency on something that itself > > has non-optional dependencies, then they should get *immediately* > > downloaded. > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
