[
https://issues.apache.org/jira/browse/MRELEASE-913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16382958#comment-16382958
]
Phil Clay commented on MRELEASE-913:
------------------------------------
Note that I contributed an example project and slightly different patch to fix
the problem in MRELEASE-920. Please evaluate the patches to ensure the best
fix. (I haven't compared the patches much more than to notice that they are
different)
> Nested properties in versions cause prepare to fail
> ---------------------------------------------------
>
> Key: MRELEASE-913
> URL: https://issues.apache.org/jira/browse/MRELEASE-913
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.5.2
> Reporter: Tim Mullender
> Priority: Minor
> Attachments: MRELEASE-913-1.patch, example.zip
>
>
> We have a multi module project in which module-b depends on module-a, the
> version of module-a in the pom for module-b is defined as a property which
> defaults to project.version
> When running release:prepare we get an error similar to the following:
> {noformat}
> The artifact (groupId:module-a) requires a different version (1.0) than what
> is found (${project.version}) for the expression (property.name) in the
> project (groupId:module-b).
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
