Hi,
Is artifact vis:canprovider-generator in reactors of the parent pom ?
If yes, there is an issue in jira [1] concerning this trouble.
If not, you need to put it in parent reactors then you will in the issue
case ;-).
I suggest you using dependencyManagement to manage dependencies beetwen
reac
This has been a point of debate. On one hand, it makes releasing a set
of modules together easier. On the other hand, it forces a new version
on your module even though you have no reason to require the new version
yet.
-Original Message-
From: LECAN Damien [mailto:[EMAIL PROTECTED]
Sen
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 phase
Hell
> 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
> 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.
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
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
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
