> Answer is no. You don't have worry about B and C because once you have > Project A depends on B & C. Once A got compiled it has all the compilation > files (B & C) inside Project A jar. For project D you don't require Project > B and C. >
just to address this advice directly: if project A's api exposes ANY of the classes from projects B or C, you would have to declare them in any case or else deal with the ClassNotFoundException. The relevance of this issue is of course superceded by the fact that maven-1 doesn't support transitive dependencies, but it's important to understand. cheers, john --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
