The acs-aem-commons subpackage isn't installing using curl command

[jerinraj5555]

I've used the below command to install the ui.apps package in my local instance and it was successful. 

curl -u admin:admin -F cmd=install http://localhost:4502/crx/packmgr/service/.json/etc/packages/ABCD/BCD.ui.apps-0.0.0-SNAPSHOT.zip

Response:
{"success":true,"msg":"Package installed"}

but in the package manager, it was showing the install state not the installed state and not able to see the last installed date as well(This issue does not happen using mvn command build ). 

Environment

AEM 6.5.16

Note: Suppose, I'm trying to install the acs-aem-commons-all-6.0.14.zip package explicitly through the curl command and I get the response as package installed but it doesn't install so we need to manually install the package every time.

curl -u admin:admin -F cmd=install  http://localhost:4502/crx/packmgr/service/.json/etc/packages/adobe/consulting/acs-aem-commons-all-6.0.14.zip

{"success":true,"msg":"Package installed"}

Can someone share any idea how this problem can be addressed? 

Thanks

[himanshu]

Your syntax looks fine as per the documentation so i am not sure why it doesn't work.

Can you try this alternate way?

curl -u admin:admin -F file=@"<zip file relative path to current folder>" -F name="<package-name>" -F install=true http://localhost:4502/crx/packmgr/service.jsp

[aanchal-sikka]

Hello @jerinraj5555 

Some packages take a bit of time to Install. If you check during this window the CRX package manager will not show it to be in installed state.

Verify logs during this time, if its tailing with logs relevant to the package then wait. Cross-check again after some time.

The curl command passes over the message to AEM to install the package. The status doesn't mean that its installed.

[jerinraj5555]

I couldn't see the below logs at the time of redeployment of acs-aem-commons-ui.content and acs-aem-commons-ui.apps that's why it's skipping the subpackage installation.

27.11.2023 13:09:26.122 *INFO* [qtp1057121915-7578] org.apache.jackrabbit.vault.packaging.impl.ActivityLog adobe/consulting/.snapshot:acs-aem-commons-ui.content:6.0.14: CREATE
27.11.2023 13:09:26.333 *INFO* [qtp1057121915-7578] org.apache.jackrabbit.vault.packaging.impl.ActivityLog adobe/consulting/.snapshot:acs-aem-commons-ui.content:6.0.14: SNAPSHOT

27.11.2023 13:09:24.673 *INFO* [qtp1057121915-7578] org.apache.jackrabbit.vault.packaging.impl.ActivityLog adobe/consulting/.snapshot:acs-aem-commons-ui.apps:6.0.14: CREATE
27.11.2023 13:09:25.594 *INFO* [qtp1057121915-7578] org.apache.jackrabbit.vault.packaging.impl.ActivityLog adobe/consulting/.snapshot:acs-aem-commons-ui.apps:6.0.14: SNAPSHOT 

[aanchal-sikka]

Hello @jerinraj5555 

We do not need to deploy the packages with each deployment. If its available in the environment with right version number, its enough.

You should keep it as a dependency, so thats its installed when anyone sets up their local, deploys on a new instance or upgrades ACS AEM commons.

Just assure that if you deploy an updated packages, its installed

[kautuk_sahni]

@jerinraj5555 Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.

[jerinraj5555]

The issue is still exist

[jerinraj5555 · Accepted solution]

I have tried the below command and it worked as expected also every time I got the Last Installed date and time for acs-aem-commons-ui-all,acs-aem-commons-ui.content and acs-aem-commons-ui.apps.

http://localhost:4502/crx/packmgr/service/.json/etc/packages/adobe/consulting/acs-aem-commons-all-6.0.14.zip -F recursive=true

Ref: https://github.com/Adobe-Consulting-Services/acs-aem-commons/issues/3228