Yes, this was definitely helpful. We'll have to rethink the way we're doing things for sure.
Just to clear one more thing up. Using the same example where libraries A and B depend on C. If Product X needs these libraries, can it just include as modules A and B or does it need C as well? That is, can a parent project just include the top-level projects or does it need to specify every component in the dependency tree? -- View this message in context: http://maven.40175.n5.nabble.com/Misunderstanding-modules-Two-or-more-projects-in-the-reactor-have-the-same-identifier-tp4614001p4616683.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
