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
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é : mard

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: 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.