...
If you are using bnd-maven-plugin
to build your OSGi bundles (what we recommend) there is a special edge case using Sling-Initial-Content and Sling i18n JSON files (example) and wrong ordering of files in the bundle ZIP file which may lead to deployment failures.
...
Code Block | ||
---|---|---|
| ||
<properties> <!-- Enable reproducible builds --> <project.build.outputTimestamp>${timestamp}<outputTimestamp>2021-05-27T00:00:00Z</project.build.outputTimestamp> </properties> |
The ${timestamp}
variable is set by a plugin in the global-parent POM and it’s value is usually automatically replace by the Maven Release Plugin on each releaseIt’s not relevant which actual timestamp value you are using here - it’s automatically updated during the release by the release or gitlflow maven plugins.
Step 4: Remove AEM Service Packs/Hotfixes
...
Remove all references to
com.adobe.cq:core.wcm.components.core
andcom.adobe.cq:core.wcm.components.all
from your parent POM.Remove all references to
com.adobe.cq:core.wcm.components.core
from your bundle POMs.Remove all references to
com.adobe.cq:core.wcm.components.all
from theconfig-definition
POM, and remove the reference to it from the CONGA Roles atconfig-definition/src/main/roles
.
Step 8: Create service users via repoinit
definition/src/main/roles
.
Step 8: Create service users via repoinit
Info |
---|
Update: It is recommended to use the OOTB principals instead of creating you own service users, see https://wcm.io/handler/configuration.html for examples. |
Some wcm.io bundles requires service users to set up appropriate permissions, and this was done in the past using CONGA-generated bundles with a file definition in the CONGA role like this wcm-io-samples-aem-cms-author-systemusers with this JSON template .
...
If you’ve not done it already, make sure you have switched all your content package projects to the Apache Jackrabbit FileVault Package Maven Plugin (see migration guide).
The latest wcm.io aem-global-parent
also includes the latest version of the FileVault Package Maven Plugin which has built-in additional validation steps, you may have to adapt your packages, see this guide .
Check/adapt all your content package module POMs:
...
If you find such a configuration, remove it completely. It will fail the image build in Adobe Cloud Manager.
NodeJS Maven Plugin
Info |
---|
Update: Latest NodeJS Maven Plugin (3.0.4 and up) should fix this problem. |
If you encounter problems with building your frontend code by Adobe Cloud Manager consider switching from wcm.io NodeJS Plugin to frontend-maven-plugin. See configuration example.
...
Filter by label (Content by label) | ||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Page Properties | ||
---|---|---|
| ||
|