Hi @nbg19a you need to use try-with-resources statement to get the resourceresolver so that it closes the session properly when it closes the resourceresolver.

Hi @NicholeVe The best approach would be to use the AEM Launches for this one to create the updated content or complete site. or if you have created the pages at the same level and want to move to the new hierarchy, you can also use the ACS commons tool- Renovator (https://adobe-consulting-services....

Hi @nitish-jain  the best practices recommend not to use it like this and always fetch the resourceresolver with try-with-resources statement in Java as it is used to automatically close resources that implement the AutoCloseable or Closeable interfaces. best way to main a common user is to define t...

Hi, please follow these steps create config under /conf/<project>/sling:configs with name as com.adobe.cq.wcm.core.components.internal.services.pdfviewer.PdfViewerCaConfigsample<com.adobe.cq.wcm.core.components.internal.services.pdfviewer.PdfViewerCaConfigjcr:primaryType="nt:unstructured"clientId="<...

Hi @Kk35 , These are dependent on the runmode configuration you used to setup your instance.whenever you setup a instance(local, on prem) you can define the runmodes by either passing the arguments while starting up or setting up in sling.properties(crx-quickstart/conf/sling.properties) file.in the ...

Hi @vashishth47  Please refer to https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/assets/admin/assets-api-content-fragmentsand swagger API for request creation: https://developer.adobe.com/experience-manager/reference-materials/6-5/assets-api-content-fragments/inde...

Hi @RK7 , Try adding the scope as test in the gson dependency. <!-- https://mvnrepository.com/artifact/com.google.code.gson/gson --><dependency><groupId>com.google.code.gson</groupId><artifactId>gson</artifactId><version>2.8.5</version><scope>test</scope></dependency>

Hi @cgseymour917 , Both are the implementations of the Java Platform only, mostly its related to different licensing authorities but the core functionality remains the same.So ideally, all the scripts should work fine.

Hi @dylanmccurry  I would recommend using IntelliJ as this won't come up over there. or whenever such issue happens you can either manually delete the target folder or restart the vs code and it will work.