...
| Binary Type | Group ID | Artifact ID | Classifier | Version | Extension |
|---|---|---|---|---|---|
| Full Release (Quickstart) | adobe.binary.aem.<aem-version>.quickstart | aem-quickstart | From Quickstart JAR | jar | |
| Service Pack (SP) | adobe.binary.aem.<aem-version>.servicepack | Package name without version | Package Version | zip | |
| Cumulative Fix Pack (CFP) | adobe.binary.aem.<aem-version>.cumulativefixpack | Package name without version | Package Version | zip | |
| Oak Cumulative Fix Pack (COFP) | adobe.binary.aem.<aem-version>.cumulativeoakfixpack | Package name without version | Package Version | zip | |
Hotfix (HF) | adobe.binary.aem.<aem-version>.hotfix | Package name without version | Package Version | zip | |
| Feature Pack (FP) | adobe.binary.aem.<aem-version>.featurepack | Package name without version | Package Version | zip | |
| Overlay | adobe.binary.aem.<aem-version>.overlay | Package name without version | Package Version | zip | |
| AEM Dispatcher | adobe.binary.aem.dispatcher | dispatcher | Platform identifier | Version | tar.gz or zip |
...
<aem-version>is the first two digits of the AEM version number e.g. "61", "62", "63"- We put Hotfix (HF) and Oak Cumulative Fix Pack (COFP) in the same group because the package names for COFP are also named "hofix"
- Examples for splitting up a package file name from Adobe into Artifact ID and Version:
AEM-CFP-6.3.0.2-2.0.zip=> Artifact IDAEM-CFP-6.3.0.2, Version:2.0cq-6.3.0-hotfix-17649-1.0.zip=> Artifact ID:cq-6.3.0-hotfix-17649, Version:1.0AEM-6.2-Service-Pack-1-6.2.SP1.zip=> Artifact ID:AEM-6.2-Service-Pack-1, Version:6.2.SP1
- For dispatcher the "Platform" makes up the string after between "dispatcher" and the version name - examples:
dispatcher-apache2.4-linux-i686-ssl-4.2.2.tar.gz=> Artifact ID:dispatcher, Classifier:apache2.4-linux-i686-ssl, Version:4.2.2, Extension:tar.gzdispatcher-iis-windows-x64-4.2.2.zip=> Artifact ID:dispatcher, Classifier:iis-windows-x64, Version:4.2.2, Extension:zip
- It is recommended to upload for Hotfixes also a readme.txt file containing a hint about what is contained in the hotfix (e.g. description from package share, list of issues that was fixed). Use same Maven coordinates as the hotfix package, plus
readmeas classifier andtxtas extension. - It is questionable if overlays should be deployed as individual artifact in the Maven Artifact Repository. It may make more sense to include them in the delivery package of your application.
Examples
Examples for Dependencies following this convention:
...