> 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?
You are getting modules, dependencies and artifacts mixed up. The module concept is simply a convenient way for building an application which is composed of several parts. Say top (parent) project A has modules B and C In sum those 3 projects produce artifacts A (perhaps via assembly plugin), B and C. Then in project X, if you need to use functionality provided by artifact B, then you add a dependency on B. You would not actually move the project B to be under X, simply add a dependency to the artifact produced by project B. As Barrie has already stated multiple times, you really must stop your work and read an eBook on Maven so this is all much clearer. You have skipped some important early steps in trying to learn Maven. Wayne --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
