On 17/01/2008, Simon Kitching [EMAIL PROTECTED] wrote:
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
Guillaume Lederrey [EMAIL PROTECTED] schrieb:
On 17/01/2008, Simon Kitching [EMAIL PROTECTED] wrote:
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
What you could possibly do is create a profile that you would use for
compiling. In this profile, add the problem dependencies with scope of
compile. But in the main part, add the problem dependencies with scope of
runtime, so that projects which just *use* your code (via its pom) see the
lib
You give not so much information, but I think I know why Maven didn't
downloaded the dependencies. Because it didn't have to.
It wil only download dependencies if it has too. If you specify a dependency
and need the transitive dependencies for compile time, you will need to add
them yourself.
Nick: for maven2, if a pom declares a dependency on something that itself has
non-optional dependencies, then they should get *immediately* downloaded.
cmd: is the small bit of config you originally posted nested inside a
dependencyManagement section? If so, that is wrong.
Otherwise, please
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
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
