We are currently adding a package (acs-commons in this case) to our Maven project as a subpackage. We need that subpackage to "merge" instead of "replace" since subpackages get installed after the project package. This is our configuration for the content-package-maven-plugin:
<plugin>
<groupId>com.day.jcr.vault</groupId>
<artifactId>content-package-maven-plugin</artifactId>
<extensions>true</extensions>
<configuration>
<filterSource>${basedir}/META-INF/vault/filter.xml</filterSource>
<verbose>true</verbose>
<failOnError>true</failOnError>
<group>HealthNow</group>
<embeddeds>
<!-- From project/core module -->
<embedded>
<groupId>this.is.our.group</groupId>
<artifactId>core</artifactId>
<target>/apps/myproject/install</target>
</embedded>
<!-- Scripting console for Felix -->
<embedded>
<groupId>org.apache.sling</groupId>
<artifactId>org.apache.sling.scripting.console</artifactId>
<target>/apps/myproject/install</target>
</embedded>
</embeddeds>
<subPackages>
<subPackage>
<groupId>com.adobe.acs</groupId>
<artifactId>acs-aem-commons-content</artifactId>
<filter>true</filter>
</subPackage>
</subPackages>
</configuration>
</plugin>
I can't find any documentation about most of the configuration options. The documentation on the content-package-maven-plugin only provides you with the configuration options for each goal, but not how to use them. Within the <subpackage> configuration, is there a way to "merge" that package instead of the default "replace?" Or will the subpackage's own filter file ALWAYS dictate the behavior?
