Adding content-package-maven-plugin resolution error for reference: 16:26:04 [ERROR] Unresolveable build extension: Plugin com.day.jcr.vault:content-package-maven-plugin:1.0.2 or one of its dependencies could not be resolved: Could not find artifact com.day.jcr.vault:content-package-maven-plugin:jar...
16:26:04 [ERROR] Unresolveable build extension: Plugin com.day.jcr.vault:content-package-maven-plugin:1.0.2 or one of its dependencies could not be resolved: Could not find artifact com.day.jcr.vault:content-package-maven-plugin:jar:1.0.2 in central
@kirankumark9814 Have you updated the configuration in publish instance? If not, you can have the config file as part of your code package and install it on publish server where you are accessing the page on.
Hi @Heena06 ,From your logs, your replication agent is configured to point to "localhost:8080". Is your publish server up and running on this port? Please confirm.
@srikanthp689160 Do you see any error in the network tab when you upload the image? A 403 error like? If yes, it could be due to a dispatcher or a firewall block. Since you have already verified dispatcher rules, please look out for firewall rules.All the domain URLs are usually behind a firewall, w...
@karthik-elumalai You can access AEM author only with a valid authentication. If not with SSO, you can use usernames and corresponding passwords to reach AEM author.Basic Auth is the simplest. Add a "Authorization" header to your request to AEM author with value "Basic Base64(uname:pwd)". Base64(u...
@kaushal_mall Thanks for that, this very well explains why a profile or partial build is not an option for AEM Cloud Service. At the same time, as @Shashi_Mulugu mentioned isn't it a downside for large orgnaisations that host all their tenants on a single AEM instance and if they want to roll out mi...