On 12 May 2010 17:34, Chris Blunck <[email protected]> wrote: > The problem I have arises when app1 and app2 use different versions of the > commons module. If app1 references commons/1.0.0 as a dependency and app2 > references commons/2.0.0 as a dependency I'm in trouble because my top level > pom.xml can't build both versions of commons in the same reactor.
Didn't this change in Maven 3? "Excellent! Maven 3 now supports modules with same groupId:artifactId in same reactor build." -- Alin Dreghiciu, http://twitter.com/adreghiciu/status/8676756095 Martin --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
