RE : RE : [Release plugin] Dependency versions not updated in rewrite-for-development phase
Great but take care of this. (perso I have some trouble with this)
Issues related :
- http://jira.codehaus.org/browse/MNG-2339
- http://jira.codehaus.org/browse/MSUREFIRE-124
Try the patch provided http://jira.codehaus.org/browse/MRELEASE-91.
This patch rewrite poms for dev phase with next dev version for
dependencies in reactors.
It's by default.
Maybe we can/should (?) add a property in release:prepare mojo which
says rewrite reactors dependencies with next true/false (true by
default) (it's not difficult)
But a maven dev must try/apply the patch before.
Other users can add a comment/vote.
--
Olivier
-Message d'origine-
De : LECAN Damien [mailto:[EMAIL PROTECTED]
Envoyé : lundi 5 juin 2006 18:53
À : Maven Users List
Objet : RE: RE : [Release plugin] Dependency versions not updated in
rewrite-for-development phase
Is artifact vis:canprovider-generator in reactors of the parent pom ?
Yes, thanks to module declaration in pom parent.
I suggest you using dependencyManagement to manage
dependencies beetwen
reactors in a multi modules build.
Because in this case you just need to change only one pom. (actually a
by hand change is needed)
Ok, release:prepare and perform works with that. I used ${pom.version}
instead of version label in pom parent for dependencyManagement, and I
worked perfectly (nothing to change by hand after release).
Thanks
Damien
-
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]
RE : RE : [Release plugin] Dependency versions not updated in rewrite-for-development phase
Reactors are in modules. Look at the test cases provided in the issue. especially at the poms in this http://jira.codehaus.org/secure/attachment/20889/snapshots-reactor-in-de pendency-management.tar -- Olivier -Message d'origine- De : LECAN Damien [mailto:[EMAIL PROTECTED] Envoyé : mardi 6 juin 2006 14:25 À : Maven Users List Objet : RE : [Release plugin] Dependency versions not updated in rewrite-for-development phase This patch rewrite poms for dev phase with next dev version for dependencies in reactors. How to know if a module is in the reactor ? Because it appears in dependencyManagement/ section ? Because it appears in modules/ section ? If this is the second solution, is there a link between the name of the folder's project and the name specified in the pom of this project ? Thanks Damien - 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]
Re: RE : [Release plugin] Dependency versions not updated in rewrite-for-development phase
a module is in reactor when it's in module/ Actually, it's better to have module name (declare in modules/) = folder name = artifactId Emmanuel LECAN Damien a écrit : This patch rewrite poms for dev phase with next dev version for dependencies in reactors. How to know if a module is in the reactor ? Because it appears in dependencyManagement/ section ? Because it appears in modules/ section ? If this is the second solution, is there a link between the name of the folder's project and the name specified in the pom of this project ? Thanks Damien - 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]
RE: RE : [Release plugin] Dependency versions not updated in rewrite-for-development phase
Is artifact vis:canprovider-generator in reactors of the parent pom ?
Yes, thanks to module declaration in pom parent.
I suggest you using dependencyManagement to manage
dependencies beetwen
reactors in a multi modules build.
Because in this case you just need to change only one pom. (actually a
by hand change is needed)
Ok, release:prepare and perform works with that. I used ${pom.version} instead
of version label in pom parent for dependencyManagement, and I worked perfectly
(nothing to change by hand after release).
Thanks
Damien
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
