[MPOM-218] consider impact of maven-remote-resources-plugin in plugins not pluginManagement

**[Adrian Cole](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=adriancole)** opened **[MPOM-218](https://issues.apache.org/jira/browse/MPOM-218?redirect=false)** and commented

While maven-remote-resources-plugin in plugins, it is difficult to work with vs if it were in pluginManagement. For example, the parent pom can spit out a distracting empty DEPENDENCIES file, which ends up by default in the source distribution.

I've noticed multiple projects (ex dubbo, edgent) creating separate distribution modules which on one hand works around this issue, but on the other is a source of maintenance.

I'd ask to consider using pluginManagement instead, or possibly having the ability to not create a DEPENDENCIES file when there are none, which would also solve the problem. Maybe there's also another way to strip this out with an assembly, but I've failed to figure this out.

---

**Affects:** ASF-16, ASF-24

**Issue Links:**
- [MPOM-134](https://issues.apache.org/jira/browse/MPOM-134) Add profile to use a different resource bundle for incubator projects

**Remote Links:**
- [workaround
](https://github.com/apache/incubator-zipkin-brave-karaf/pull/39)

2 votes, 4 watchers

Start by inspecting the parent POM configuration for maven-remote-resources-plugin and how it affects source distributions. Compare pluginManagement with the current plugins placement and the proposed option to suppress an empty DEPENDENCIES file; done means avoiding distracting empty output without breaking dependency-resource generation.

Written by the indexing model from the issue text.