It appears from the error message that the <useProxy> tag is placed after the </extensions> tag, which is incorrect. The tag must be placed under the <configuration> tag of the <plugin>. Please have a look at my previous examples on how to use <useProxy>.

The error may occur because Maven is attempting to use system or IDE proxy settings when connecting to http://localhost:4502/crx/packmgr/service.jsp, which causes the request to be redirected (HTTP 301) instead of being processed directly by your local AEM instance.Try to disable proxy usage for the...

You can try one of these.Basic logging:-Xlog:gc*=info:file=/path/to/gc.log:time,uptime,level,tagsDetailed logging:-Xlog:gc*=info,gc+phases=debug:file=/path/to/gc.log:time,uptime,level,tagsComplete debug-level logging:-Xlog:gc*=debug:file=/path/to/gc.log:time,uptime,level,tags  

Since the workflow does not trigger for you (as the environment admin) but does work for other users in the admin group, the most likely explanation is that, as the admin, you have access to AEM Workflow, JCR privileges, and OSGi configuration. However, your custom group does not have full workflow ...

hi @sams16001423, With the touch UI, this is possible out of the box. See this page for a detailed explanation: https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/sites/authoring/workflows/applying. I want to highlight that you can select multiple nodes before clicki...

If SARB core is your project repository, have you checked if org.apache.xmlbeans is listed as a dependency? If so, you should upload it to the version inside AEM. Also, have you updated in your project pom.xml the dependency to match the new AEM version?<!-- https://mvnrepository.com/artifact/com.ad...

Hi @Murali__D,Upgrading Java may be painless, but upgrading to JUnit 5 is not an easy task and requires many code changes. The most likely root causes in your case include:JUnit migration requirements: JUnit 5 has a completely different architecture than JUnit 4, with different annotations, assertio...

Custom Oak indexes should be placed in the ui.apps package under the path ui.apps/src/main/content/jcr_root/_oak_index/. This is the correct location, and you don't need a separate structure package for Oak indexes.This page explains everything about preparing the new index definition, deploying cus...

the plugin content-package-maven-plugin at version 1.0.4 no longer handles the content-package packaging type, which is why Maven doesn't recognize it.Add filevault-package-maven-plugin (for building content packages):<plugin> <groupId>org.apache.jackrabbit</groupId> <artifactId>filevault-pa...

If SARB core is your project repository, have you checked if org.apache.xmlbeans is listed as a dependency? If so, you should upload it to the one inside AEM. Also, have you updated in your project pom.xml the dependency to match the new AEM version?<!-- https://mvnrepository.com/artifact/com.adobe....