[MRELEASE-878] Exclude generated dependency-reduced-pom.xml and flattened-pom.xml

**[Mirko Friedenhagen](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=mfriedenhagen)** opened **[MRELEASE-878](https://issues.apache.org/jira/browse/MRELEASE-878?redirect=false)** and commented

As stated in MOJO-2030 and MSHADE-145, both plugins create additional poms in `basedir` to avoid confusion while generating the site.

This will lead to an error during `release:prepare`, so just exclude `dependency-reduced-pom.xml` and `flattened-pom.xml` by default as well.

---

**Affects:** 2.5

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

- [MSHADE-124](https://issues.apache.org/jira/browse/MSHADE-124) Need better plan for getting dependency-reduced-pom.xml out of basedir

2 votes, 4 watchers

Start at the release:prepare entry point and locate the default file-exclusion configuration. Check how generated files in basedir are handled, using dependency-reduced-pom.xml and flattened-pom.xml as the target names. Done means both files are excluded by default and release:prepare no longer reports them as unexpected files.

Written by the indexing model from the issue text.