[MRELEASE-913] Nested properties in versions cause prepare to fail

**[Tim Mullender](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=tjmullender)** opened **[MRELEASE-913](https://issues.apache.org/jira/browse/MRELEASE-913?redirect=false)** and commented

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:

```
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).
```

---

**Affects:** 2.5.2

**Attachments:**
- [example.zip](https://issues.apache.org/jira/secure/attachment/12734572/example.zip) (_18.94 kB_)
- [MRELEASE-913-1.patch](https://issues.apache.org/jira/secure/attachment/12735712/MRELEASE-913-1.patch) (_17.89 kB_)

**Issue Links:**
- [MRELEASE-920](https://issues.apache.org/jira/browse/MRELEASE-920) release:prepare does not resolve recursive properties
(_**"is duplicated by"**_)

4 votes, 6 watchers

Start by unpacking example.zip and reproducing the failure with release:prepare; compare the behavior with MRELEASE-913-1.patch and inspect the linked MRELEASE-920 issue about recursive properties. Done means nested properties resolve to the module dependency version and release:prepare completes without the reported mismatch.

Written by the indexing model from the issue text.