[mojo-dev] [jira] (MVERSIONS-123) Version properties inparent not picked up by e.g. display-property-updates

[Sergei Ivanov (JIRA)]

Title: Message Title

Sergei Ivanov commented on an issue   Re: Version properties inparent not picked up by e.g. display-property-updates I think that there are two possible views on the same problem, and that is why it is confusing to many people. 1. How the plugin views it at the moment (to the best of my understanding): a) collect all properties defined locally in the POM b) identify which of those properties are locally used in dependency version specifications c) check for dependency version updates corresponding to that subset of properties 2. How many people intuitively assume is: a) walk through all locally declared dependencies and dependency management in the POM b) extract property references from version specifications of those managed and unmanaged dependencies c) check for dependency version updates corresponding to that subset of properties The difference is that the second approach can yield a larger subset of properties, some of which might not be locally defined, but inherited. Before the invention of BOMs and import scope, people used inheritable properties to provide a coherent version for a large number of modules of a 3rd-party library. That saved the effort going through the hassle of setting up dependency management for each and every possibly used module in the parent POM. Think of Spring framework: one would declare the spring.version=2.5.6 property in the parent POM and let the descendant POMs refer to it when declaring dependencies on spring-beans, or spring-web, or spring-whatever. Setting up dependency management for spring-beans, spring-web, spring-whatever and a dozen other Spring libraries (some of them would never be used, but just in case) in the parent POM would be a major hassle compared to just a single property declaration. Given that provided BOMs are still rare, the problem is still actual to this day. Add Comment   Mojo's Versions Maven Plugin / MVERSIONS-123 Version properties inparent not picked up by e.g. display-property-updates 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. Example: If module *B* has a dependency on module A, declared in B as follows: <dependency> <groupId>com.my.test</groupId> <artifactId>module-A</artifactId> <ve... This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email