Thanks for the pointer, Kenney. I have attached a patch and patched binary to the issue which fixes the problem for me.
-----Original Message----- From: Kenney Westerhof [mailto:[EMAIL PROTECTED] Sent: Friday, June 09, 2006 10:26 AM To: Maven Developers List Subject: Re: multi-module build versions On Fri, 9 Jun 2006, Mike Perham wrote: Hi, It's a bug. See http://jira.codehaus.org/browse/MNG-1245. -- Kenney > I started this thread over on the user list but haven't seen any > replies of merit. > > http://www.nabble.com/multi-module-build-overriding-dependency-version > s- > t1758915.html > > In summary, I have two projects: domain and services. Both projects > are at version 1.2.2-SNAPSHOT. services 1.2.2-SNAPSHOT depends on > domain 1.2.1. When I try to build both in a multi-module build, > services is getting domain 1.2.2-SNAPSHOT in its classpath, not 1.2.1. > > When I turn on debugging I see this: > > [DEBUG] active project artifact: > artifact = com.webify.fabric:fabric-pm-domain:jar:1.2.1:compile; > project: [EMAIL PROTECTED] > (selected for compile) > > The problem is that the domain's project version in the reactor is > 1.2.2-SNAPSHOT but the dependent artifact's version is 1.2.1. Why > isn't Maven taking the version into account when "overriding" the > dependency to replace it with the project during build? > > mike > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] For > additional commands, e-mail: [EMAIL PROTECTED] > > -- Kenney Westerhof http://www.neonics.com GPG public key: http://www.gods.nl/~forge/kenneyw.key --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
