[MRELEASE-653] Filter reactor projects that are concerned by a submodule branch operation

**[Lucien Weller](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=lucien@wellernet.ch)** opened **[MRELEASE-653](https://issues.apache.org/jira/browse/MRELEASE-653?redirect=false)** and commented

We have the requirement to create a separate branch of one submodule when releasing the entire project. We solved this with the follwoing config in pom.xml of concerned submodule:

```xml

branchSubModule



org.apache.maven.plugins
maven-release-plugin
false


explorer-branch
false
package

branch


re${project.version}-submodule
${project.version}
true
${project.version}-00-SNAPSHOT

```

We launch the release build of parent project with:

`mvn release:prepare release:perform -DreleaseProfiles=branchSubModule`

Beside issue adressed by MRELEA[SE-619](https://issues.apache.org/jira/browse/SE-619), we also face the problem that all submodules are affected when our special submodule gets branched.

We solved this issue by filtering reactor projects with the current working path.

---

**Affects:** 2.1

**Attachments:**
- [filter-modules.patch](https://issues.apache.org/jira/secure/attachment/12717933/filter-modules.patch) (_1.81 kB_)

**Issue Links:**
- [MRELEASE-619](https://issues.apache.org/jira/browse/MRELEASE-619) release:branch doesn't work as expected with multi-module projects
(_**"depends upon"**_)