On Thu, Jul 21, 2011 at 3:28 AM, kanesee <kane...@gmail.com> wrote: > Hi Wayne, > > Yes, I understand I don't have to have to depend on C from product X, but do > I need to include it as a module?
Re-read my message, well actually I should have written this Modules != Dependencies All Modules really do is make maven run the same command in the module. It tells you nothing about the dependency structure. I suggest again to go have a read of the books. In it you will find the best practices on when to declare a dependency. e.g. If Product X makes direct use of API from library C then you should declare it as a dependency in Product X. If Product X doesn't use the API from library C, then you don't need to declare it, but it will be pulled in via transitive dependencies because you depend on A or B. The best practice being that you clearly declare all dependencies that your artifact is using rather than relying on the smoke and mirrors of transitive dependencies. mvn dependency:analyze can help you in validating this (but some thought it required for test scopes) --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
