I found this reference to my problem: http://dspace.2283337.n4.nabble.com/DSpace-1-7-0-amp-Maven-3-0-2-DuplicateProjectException-Missing-pom-xml-properties-td3339149.html
So Maven 3 removed the "enable nested module" option from the earlier version? I guess that might have helped with my situation. Does anyone have any other info about this? Maybe there's another workaround...? If not, I'll have to reorganize my company's entire dependency hierarchy, which is less than desirable. -Kane -- View this message in context: http://maven.40175.n5.nabble.com/Misunderstanding-modules-Two-or-more-projects-in-the-reactor-have-the-same-identifier-tp4614001p4614028.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
