[MSHADE-124] Need better plan for getting dependency-reduced-pom.xml out of basedir

**[Benson Margulies](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=bmargulies)** opened **[MSHADE-124](https://issues.apache.org/jira/browse/MSHADE-124?redirect=false)** and commented

MSHADE-123 reported that putting the d-r-p into some location other
than 'basedir' causes 'basedir' to follow it around, which can break builds.

This is hard to fix, given the core maven definition of basedir as 'the dir containing the pom' with no option to change it.

---

**Affects:** 1.7.1

**Issue Links:**
- [MSHADE-160](https://issues.apache.org/jira/browse/MSHADE-160) change default location of dependency-reduced-pom.xml
(_**"blocks"**_)
- [MSHADE-329](https://issues.apache.org/jira/browse/MSHADE-329) Concurrent writes of dependency-reduced-pom.xml adds same exclusion ad infinitum

- [MRELEASE-878](https://issues.apache.org/jira/browse/MRELEASE-878) Exclude generated dependency-reduced-pom.xml and flattened-pom.xml

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

- [MSHADE-123](https://issues.apache.org/jira/browse/MSHADE-123) 1.7 Causes failures in other plugins make "basedir" point to the build dir

**Remote Links:**
- [GitHub Pull Request #128
](https://github.com/apache/maven-shade-plugin/pull/128)

2 votes, 6 watchers

Start by reading the linked MSHADE-123 report about basedir behavior and MSHADE-160 about changing the default dependency-reduced-pom.xml location. Review the related MSHADE-145, MSHADE-329, and MRELEASE-878 issues and Pull Request #128. Done requires an agreed approach that keeps Maven's basedir semantics from breaking builds.

Written by the indexing model from the issue text.