changing version of module and dependent modules

[Marcin Gurbisz <gu...@poczta.onet.pl>]

I would like to have possibility to change version of specific library 
in all project.xml files all over the project..
To make it clearer I give an example:
Module A and B depends on C, and I want to change version of C. After 
executing some goal I would expect that version of module C and all 
dependent would change.
Have anyone solved this problem or you are dealing with it in diferent way?
I've looked at release plug-in and it seems to me that it change only 
version in "C" module. Am I right?
I've been using xml entities to ensure project consistency so this 
problem hasn't occurred but I want to get rid of entities.

Thanks in advance,
Marcin


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: changing version of module and dependent modules

[Milos Kleint <Mi...@sun.com>]

Marcin Gurbisz wrote:

> I would like to have possibility to change version of specific library 
> in all project.xml files all over the project..
> To make it clearer I give an example:
> Module A and B depends on C, and I want to change version of C. After 
> executing some goal I would expect that version of module C and all 
> dependent would change.
> Have anyone solved this problem or you are dealing with it in diferent 
> way?
> I've looked at release plug-in and it seems to me that it change only 
> version in "C" module. Am I right?
> I've been using xml entities to ensure project consistency so this 
> problem hasn't occurred but I want to get rid of entities.
>

i've added support for this scenario to mevenide for netbeans (later 
should be added to the eclipse's mevenide as well).
when a version/artifactid/groupid of a project changes, the IDE checks 
other opened projects and if they contain the artifact as dependency, 
offers one to update the other project's pom files as well. They need to 
be opened, since in maven1, there's no way to figure out who uses the 
project's artifact AFAIK, maven2 could have that done somehow I think. 
Then it probably should not be done in the IDE, but rather as a maven 
plugin.

http://mevenide.codehaus.org/download.html


hope that helps.

Milos Kleint

> Thanks in advance,
> Marcin
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org