[MRELEASE-798] Commit additional files with release plugin

**[Thorsten Hoeger](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=hoegertn)** opened **[MRELEASE-798](https://issues.apache.org/jira/browse/MRELEASE-798?redirect=false)** and commented

Hi,

is there any possibility to have the release-plugin commit additional files which were
generated/modified in the preparationGoals.

Now only the pom.xml is commited. Using scm-plugin has some serious drawbacks in this
situation.

If it is not possible at the moment, is there any chance to get this in the future. Maybe
there could be a parameter additionalCommitFiles with a list of files to commit along with
pom.xml.

---

**Affects:** 2.3.2

**Attachments:**
- [maven-release-2.4.1-additionalCommitted.patch](https://issues.apache.org/jira/secure/attachment/12718202/maven-release-2.4.1-additionalCommitted.patch) (_12.32 kB_)

**Issue Links:**
- [MSHADE-145](https://issues.apache.org/jira/browse/MSHADE-145) Site not generated correctly when overriding dependencyReducedPomLocation with relocation

- [MRELEASE-51](https://issues.apache.org/jira/browse/MRELEASE-51) release:perform could update the date attribute in the changes.xml

**Remote Links:**
- [GitHub Pull Request #20
](https://github.com/apache/maven-release/pull/20)
- [GitHub Pull Request #4
](https://github.com/apache/maven-release/pull/4)

7 votes, 10 watchers

Start by reading the release-plugin flow around preparationGoals and the existing pom.xml commit, then review the attached maven-release-2.4.1-additionalCommitted.patch and the referenced pull requests. Done means generated or modified files can be configured and committed alongside pom.xml without relying on the scm-plugin workaround.

Written by the indexing model from the issue text.