Open kwin opened 4 years ago
Issue in help/sites-deploying/in-place-upgrade.md
In section "Determining the correct upgrade start command" it says: Modify the command by replacing the path to the existing jar ( crx-quickstart/app/aem-quickstart*.jar in this case) with the new jar that is a sibling of the crx-quickstart folder.
The problem is that the CLI parameter c has a different meaning for the app/aem-quickstart*.jar than for the main jar. For the former it is specifying the sling.home = crx-quickstart folder (https://sling.apache.org/documentation/the-sling-engine/the-sling-launchpad.html#command-line-options), while for the latter it is the HTTP Servlet Context Path (https://docs.adobe.com/content/help/en/experience-manager-65/deploying/deploying/custom-standalone-install.html#further-options-available-from-the-quickstart-file). If you take over parameter -c crx-quickstart, AEM will start with the HTTP Servlet Context Path crx-quickstart.
c
-c crx-quickstart
crx-quickstart
CQDOC-15551
guillaumecarlino
commented
1 year ago
Issue in help/sites-deploying/in-place-upgrade.md
In section "Determining the correct upgrade start command" it says: Modify the command by replacing the path to the existing jar ( crx-quickstart/app/aem-quickstart*.jar in this case) with the new jar that is a sibling of the crx-quickstart folder.
The problem is that the CLI parameter
chas a different meaning for the app/aem-quickstart*.jar than for the main jar. For the former it is specifying the sling.home = crx-quickstart folder (https://sling.apache.org/documentation/the-sling-engine/the-sling-launchpad.html#command-line-options), while for the latter it is the HTTP Servlet Context Path (https://docs.adobe.com/content/help/en/experience-manager-65/deploying/deploying/custom-standalone-install.html#further-options-available-from-the-quickstart-file). If you take over parameter-c crx-quickstart, AEM will start with the HTTP Servlet Context Pathcrx-quickstart.