[mojo-dev] [jira] (MVERSIONS-186) Changing properties (e.g. versions:update-property) doesn't work if the property and its reference are in separate poms

[Fabrizio Giudici (JIRA)]

Fabrizio Giudici commented on MVERSIONS-186 Changing properties (e.g. versions:update-property) doesn't work if the property and its reference are in separate poms I don't have <version> for each <dependency> in modules - actually the $ {property} is in a <dependency> item inside a <dependencyManagement> section. My fault for not having described it correctly - I've updated the description of the problem. There's a three-level structure of POMs: one master POM, one child POM at the second level, the actual modules at the third level. Versions are only listed in a single <dependencyManagement> section in the second-level POM; properties are listed in the Master POM. And the version:update plugin doesn't work with this configuration. It's not as important as when I filed it, but I still think it's a bug.

This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email