You are right, building B by itself works as expected. That's why I said "multi-module build" in the subject.
But this is for integration build purposes. I want to build the tip every time there is a checkin to ensure the system is stable. So I kick off the build in root and expect everything beneath to build. -----Original Message----- From: Henry S. Isidro [mailto:[EMAIL PROTECTED] Sent: Thursday, June 08, 2006 7:18 PM To: Maven Users List Subject: Re: multi-module build overriding dependency versions On Friday, June 9, 2006 07:36, Mike Perham wrote: > I have a set of modules: > > root/ > a/ > b/ > > Both modules are at version 1.1.2-SNAPSHOT and B depends on version > 1.1.1 of A. > > When I run the root build, it builds A and B and version > 1.1.2-SNAPSHOT of A is forced upon B. This is a massive problem for > us as it means we can't do independent development of modules - the > unfinished API of A is pushed upon B even though B explicitly says it > wants a particular version. > Can't you try building from B? I think running from B would pull in the correct version of A. I don't know the reason why running from root exhibits this behavior but I remember reading about it in the user list some time back. I just can't seem to find it. - Henry --------------------------------------------------------------------- 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]
