Resolution: Not A Bug
Affects Version/s: 1.2
Fix Version/s: None
Java(TM) SE Runtime Environment (build 1.6.0_18-b07)
Java HotSpot(TM) Client VM (build 16.0-b13, mixed mode, sharing)
Number of attachments :
The goals operating on property controlled version numbers (e.g. display-property-updates) only work if the properties are defined in the targeted POM itself, not in a parent POM.
If module B has a dependency on module A, declared in B as follows:
is not defined in B's own POM, but its parent, then the plugin doesn't pick it up - it simply says:
"This project does not have any properties associated with versions"
This is a major problem for us, since all our dependency version properties are defined in each project's root POM, i.e. the parent of all sub-modules in that project.