[MSHADE-323] Flatten Maven Plugin conflicts with Maven Shade Plugin

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

When using Flatten Maven Plugin in the same project with Maven Shade Plugin then the dependency reduced POM is _not_ flattened.

What i encountered that having flatten plugin configured according to https://maven.apache.org/maven-ci-friendly.html, and having shade plugin configured with the default settings to produce uber jar the ${revision} variable remains and gets installed/deployed within the final pom, thus making the pom in the repository invalid.

It seems that both plugins transform original pom. And then what gets installed in the last one, which is the 'shades' one. I'm not sure that's a bug (in a sense that it is shade's fault).

See also https://github.com/mojohaus/flatten-maven-plugin/issues/100

---

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

6 votes, 6 watchers

Reproduce the interaction between Flatten Maven Plugin and Maven Shade Plugin using the Maven CI-friendly configuration and Shade's default settings. Inspect the reduced POM that is installed or deployed; done means the final repository POM is flattened and no longer contains the unresolved ${revision} variable.

Written by the indexing model from the issue text.