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
[mailto:[EMAIL PROTECTED]
Sent: Thu 1/17/2008 3:47 PM
To: users@maven.apache.org
Subject: about dependence transfer
i use maven2 to manage my jars
like this
dependency
groupIdorg.springframework/groupId
artifactIdspring/artifactId
automatic.
now how can i set the config file?
--
View this message in context:
http://www.nabble.com/about-dependence-transfer-tp14920281s177p14920281.html
Sent from the Maven - Users mailing list archive at Nabble.com
depended on it.
If you have further questions, please be more descriptive about what you are
trying to do.
Hth,
Nick Stolwijk
-Original Message-
From: cmd [mailto:[EMAIL PROTECTED]
Sent: Thu 1/17/2008 3:47 PM
To: users@maven.apache.org
Subject: about dependence transfer
i
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
