Two scenarios:
-
A customer has an AEM instance that has not been customized, they can use the package install method to deploy the assets-commerce maven package to the instance.
-
A customer has already customized AEM, so they need to manually integrate the code from the AEM-Commerce project.
Suggest describing these scenarios in the README for the project instead of the ExL documentation.
After describing the scenario, explain process to follow for each. (The maven package install commands are already described.)
Also, in both scenarios, Adobe recommends replacing the
<groupId>com.aemclouddemo.commerce</groupId> with something more meaningful to their project.
This step would be unnecessary if we replace the identifier in the Commerce-Assets project.
Two scenarios:
A customer has an AEM instance that has not been customized, they can use the package install method to deploy the assets-commerce maven package to the instance.
A customer has already customized AEM, so they need to manually integrate the code from the AEM-Commerce project.
Suggest describing these scenarios in the README for the project instead of the ExL documentation.
After describing the scenario, explain process to follow for each. (The maven package install commands are already described.)
Also, in both scenarios, Adobe recommends replacing the
<groupId>com.aemclouddemo.commerce</groupId>with something more meaningful to their project.This step would be unnecessary if we replace the identifier in the Commerce-Assets project.