Why Single AEM JCR package for multi-module project?

I am working as AEM Developer, I have an AEM project organized similarly to Adobe's core components project, in which the all module is in charge of building the zip that contains an embedded .jar of the bundle, and two sub packaged .zip content-packages.

When uploaded and installed to AEM via a package manager, the single zip created in all/target explodes to its 3 sub packages (core, content, and config). I want to create a single zip that keeps my project's footprint as a single package in AEM package manager.

Here is the relevant bits of my all/pom.xml (same as Adobe's core components all/pom.xml):


 
com.day.jcr.vault
 
content-package-maven-plugin
 
true
 

 
true
 
myApp
 
true
 
target/\${project.artifactId}
 

 

 
\${project.groupId}
 
myApp.core
 
/apps/myApp/install
 
true
 

 

 
true
 

 

 
\${project.groupId}
 
myApp.content
 
true
 

 

 
\${project.groupId}
 
myApp.config
 
true
 

 

 


 

 
\${project.groupId}
 
myApp.core
 
\${project.version}
 
provided
 

 

 
\${project.groupId}
 
myApp.content
 
\${project.version}
 
zip
 
provided
 

 

 
\${project.groupId}
 
myApp.config
 
zip
 
\${project.version}
 
provided
 

Thanks & Regards

Camillelola

SolidworksGeneral