Re: RE : [Release plugin] Dependency versions not updated in rewrite-for-development phase

2006-06-06 Thread Emmanuel Venisse
a module is in reactor when it's in Actually, it's better to have module name (declare in ) = 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

RE : RE : [Release plugin] Dependency versions not updated in rewrite-for-development phase

2006-06-06 Thread Olivier Lamy
nvoyé : 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

RE : [Release plugin] Dependency versions not updated in rewrite-for-development phase

2006-06-06 Thread LECAN Damien
> 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 section ? Because it appears in section ? If this is the second solution, is there a link between the name of the folder's project and

RE : RE : [Release plugin] Dependency versions not updated in rewrite-for-development phase

2006-06-06 Thread Olivier Lamy
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:canpro

RE : [Release plugin] Dependency versions not updated in rewrite-for-development phase

2006-06-05 Thread Olivier Lamy
Have a look http://jira.codehaus.org/browse/MRELEASE-91. -- Olivier -Message d'origine- De : LECAN Damien [mailto:[EMAIL PROTECTED] Envoyé : lundi 5 juin 2006 17:53 À : users@maven.apache.org Objet : [Release plugin] Dependency versions not updated in rewrite-for-development

RE: RE : [Release plugin] Dependency versions not updated in rewrite-for-development phase

2006-06-05 Thread LECAN Damien
> 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.

RE: [Release plugin] Dependency versions not updated in rewrite-for-development phase

2006-06-05 Thread Mike Perham
] Sent: Monday, June 05, 2006 10:53 AM To: users@maven.apache.org Subject: [Release plugin] Dependency versions not updated in rewrite-for-development phase Hello, I'm working with Maven 2.0.4 and maven-release-plugin 2.0-beta4. When I try to release a multi-module project, the rewrit

RE : [Release plugin] Dependency versions not updated in rewrite-for-development phase

2006-06-05 Thread Olivier Lamy
:53 À : users@maven.apache.org Objet : [Release plugin] Dependency versions not updated in rewrite-for-development phase Hello, I'm working with Maven 2.0.4 and maven-release-plugin 2.0-beta4. When I try to release a multi-module project, the rewrite-for-development phase forgets to migrate

[Release plugin] Dependency versions not updated in rewrite-for-development phase

2006-06-05 Thread LECAN Damien
Hello, I'm working with Maven 2.0.4 and maven-release-plugin 2.0-beta4. When I try to release a multi-module project, the rewrite-for-development phase forgets to migrate dependency versions. For example : ## Before vsi vsi 0.0.2-SNAPSHOT 4.0.0 vsi plugin-generator Pl