[MRELEASE-843] Child modules defined in profiles aren't updated by update-versions

**[M. Justin](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=mjjustin)** opened **[MRELEASE-843](https://issues.apache.org/jira/browse/MRELEASE-843?redirect=false)** and commented

When I do a mvn:update-versions for a multi-module project that has one of its modules defined in a profile, the modules defined in the profile don't have their versions updated. I would expect these modules to also be updated.

```

4.0.0
pom

com.example
example-parent
1.0.0-SNAPSHOT

example-module1




my-profile

example-module2

scm:git:examplerepo:example.git

```

In this example, when I execute mvn release:update-versions, I get queried to update example-parent and example-module1, but not example-module2.

---

2 votes, 4 watchers

Start by reproducing the provided multi-module example with `mvn release:update-versions`, comparing a top-level module with `example-module2` inside `my-profile`. Trace the update-versions entry point and its module traversal; done means the profile-defined module is also included in the version-update prompts and receives the new version.

Written by the indexing model from the issue text.