Works around inheritance that results in an empty DEPENDENCIES file (#39

)

org.apache:apache:21 sets maven-remote-resources-plugin in plugins, not pluginManagement
This results in execution in the parent project, and a side effect of an empty
DEPENDENCIES file in the assembly when packaged with the apache-release profile.

https://issues.apache.org/jira/browse/MPOM-218

This works around the problem by skipping at the parent level at the cost of having to
un-skip it at every deployed child.

exporter-sender-kafka/pom.xml

@@ -61,6 +61,12 @@
 
   <build>
     <plugins>
+      <plugin>
+        <artifactId>maven-remote-resources-plugin</artifactId>
+        <configuration>
+          <skip>false</skip>
+        </configuration>
+      </plugin>
       <plugin>
         <groupId>biz.aQute.bnd</groupId>
         <artifactId>bnd-maven-plugin</artifactId>

exporter-sender-okhttp/pom.xml

@@ -56,6 +56,12 @@
 
   <build>
     <plugins>
+      <plugin>
+        <artifactId>maven-remote-resources-plugin</artifactId>
+        <configuration>
+          <skip>false</skip>
+        </configuration>
+      </plugin>
       <plugin>
         <groupId>biz.aQute.bnd</groupId>
         <artifactId>bnd-maven-plugin</artifactId>

exporter/pom.xml

@@ -60,6 +60,12 @@
 
   <build>
     <plugins>
+      <plugin>
+        <artifactId>maven-remote-resources-plugin</artifactId>
+        <configuration>
+          <skip>false</skip>
+        </configuration>
+      </plugin>
       <plugin>
         <groupId>biz.aQute.bnd</groupId>
         <artifactId>bnd-maven-plugin</artifactId>

features/pom.xml

@@ -40,6 +40,12 @@
       </resource>
     </resources>
     <plugins>
+      <plugin>
+        <artifactId>maven-remote-resources-plugin</artifactId>
+        <configuration>
+          <skip>false</skip>
+        </configuration>
+      </plugin>
       <plugin>
         <artifactId>maven-resources-plugin</artifactId>
         <executions>

pom.xml

@@ -433,6 +433,22 @@
           </execution>
         </executions>
       </plugin>
+
+      <!-- org.apache:apache:21 sets maven-remote-resources-plugin in plugins, not pluginManagement
+           This results in execution in the parent project, and a side effect of an empty
+           DEPENDENCIES file in the assembly when packaged with the apache-release profile.
+
+           https://issues.apache.org/jira/browse/MPOM-218
+
+           This works around the problem by skipping at the parent level at the cost of having to
+           un-skip it at every deployed child.
+       -->
+      <plugin>
+        <artifactId>maven-remote-resources-plugin</artifactId>
+        <configuration>
+          <skip>true</skip>
+        </configuration>
+      </plugin>
     </plugins>
   </build>