Details
-
Type:
Bug
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 1.1, 1.2
-
Fix Version/s: None
-
Labels:None
-
Environment:Maven 2.2.1
-
Number of attachments :
Description
If we have a project A with modules B & C where :
- B inherit from A
- C DOESN'T inherit from A
When we execute the following command line :
mvn org.codehaus.mojo:versions-maven-plugin:1.2:set -DnewVersion=0.1
Only A & B are updated.
The fact that C doesn't inherit from A (whereas C is a module of A) doesn't make it updated.
Issue Links
- relates to
-
MVERSIONS-115
Missing version update inside dependency
-
Activity
Here is a proposed patch MVERSIONS-131_patch.txt
. The change is to simply update all projects which had the same version to start with as the reactor/aggregator POM. If the reactor/aggregator POM is the <parent> the parent version is also updated as before, but essentially it simplifies the logic by just updating all projects with the same version instead of only those projects where the parent was the reactor.
All unit tests still pass with this patch, but I did not check what the unit tests are actually testing...
Yes, this is hitting me right now and would love to get this fixed! 
Oh i spent couple hours on that, event prepared test case and then found it
Please fix it.
could any of the (core) developers please common whether
- this is an accepted bug (i.e. intended to be fixed)
- the attached patch is a legitimate and viable solution
- there are any plans in which version this might be fixed?
(We're in need of this feature, too, and I'm trying to get a feeling how far we are from getting it )
Thanks.
This has been a long standing problem for me as well. Has anyone been able to find a work-around? It does not make sense to me why this only works when the children specify the aggregator/reactor as the parent POM. Curious if it is a limitation, or a missed corner case in the code.