Techincaly speaking sure no relation ;-) But I was just speaking about how maven handles dependencies in multi modules build with reactors and how poms are rewriting for next dev phase. As MNG-1245 says, when a dependency is find in reactors (maven ignore version whereas is forced in a module). Personnaly, I like (in fact I think is a feature ;-) ) this because it ensure in a multi-module build that all last classes are used for all modules. Is not why reactor/module exists ?
Personnaly again, when I want to break this, I create branch on the module(s) which needs a patch. WDYT ? -- Olivier -----Message d'origine----- De : Mike Perham [mailto:[EMAIL PROTECTED] Envoyé : vendredi 9 juin 2006 15:42 À : Maven Users List Objet : RE: RE : multi-module build overriding dependency versions Certainly not. The bugs have no relation at all. I can increment the version in my poms by hand and get the same behavior - this has nothing to do with the release plugin. -----Original Message----- From: Olivier Lamy [mailto:[EMAIL PROTECTED] Sent: Friday, June 09, 2006 6:06 AM To: 'Maven Users List' Subject: RE : multi-module build overriding dependency versions Hi, Mike, it's certainly the main reason why (IMHO) http://jira.codehaus.org/browse/MRELEASE-91 can be considered as a bug ;-) WDYT ? -- Olivier -----Message d'origine----- De : Mike Perham [mailto:[EMAIL PROTECTED] Envoyé : vendredi 9 juin 2006 03:11 À : Maven Users List Objet : RE: multi-module build overriding dependency versions 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] This e-mail, any attachments and the information contained therein ("this message") are confidential and intended solely for the use of the addressee(s). If you have received this message in error please send it back to the sender and delete it. Unauthorized publication, use, dissemination or disclosure of this message, either in whole or in part is strictly prohibited. ------------------------------------------------------------------------ -------------------------------------- Ce message électronique et tous les fichiers joints ainsi que les informations contenues dans ce message ( ci après "le message" ), sont confidentiels et destinés exclusivement à l'usage de la personne à laquelle ils sont adressés. Si vous avez reçu ce message par erreur, merci de le renvoyer à son émetteur et de le détruire. Toutes diffusion, publication, totale ou partielle ou divulgation sous quelque forme que se soit non expressément autorisées de ce message, sont interdites. ------------------------------------------------------------------------ ------------------------------------- --------------------------------------------------------------------- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
