On 10/7/05, Brett Porter [EMAIL PROTECTED] wrote:
The reason for this difference is because if B extends a class from A,
and C uses the class from B, A is required at compile time.
Often this is not strictly necessary, but one usecase would be where
Class-from-C extends Class-from-B, which
On 10/6/05, Brett Porter [EMAIL PROTECTED] wrote:
Sorry, I'm missing something. Why isn't B depending on A with runtime scope?
B depends on A with compile scope because it directly uses classes
from A during compilation, not just at runtime.
This gives the following scenario.
C --(compile)-- B
The reason for this difference is because if B extends a class from A,
and C uses the class from B, A is required at compile time.
Otherwise, I'd agree.
- Brett
On 10/7/05, John Fallows [EMAIL PROTECTED] wrote:
On 10/6/05, Brett Porter [EMAIL PROTECTED] wrote:
Sorry, I'm missing something.
Suppose I have 3 Maven2 projects, A, B and C.
A is self-contained.
B depends on A for-implementation-only.
C depends on B.
My understanding of dependency scopes is that if C depends on B at
compile scope, then all of B's compile scope dependencies will
also become transitive compile scope
Sorry, I'm missing something. Why isn't B depending on A with runtime scope?
- Brett
On 10/6/05, John Fallows [EMAIL PROTECTED] wrote:
Suppose I have 3 Maven2 projects, A, B and C.
A is self-contained.
B depends on A for-implementation-only.
C depends on B.
My understanding of dependency
