You need to explicitly create the folders on which you are setting the ACLs  Add repoinit statements to the script property of the config. The syntax and options are documented in Sling documentation. There should be explicit creation of a parent folder before their child folders. For example, an ex...

1) Can you check which package/dependency is adding the reported on org.apache.xml.security http://localhost:4502/system/console/depfinder 2) have you updated the aem Uber jar to 6.5.17

Surely aem query will help. If you know which all components are having the href value and it only part of some specific node property then you can go with normal page property query and if you are not sure if its part of one component or several components and used extensively with many node proper...

In the cache section of your dispatcher farm configuration you can add another rule to deny caching for the error/404.html   /glob “/content/site/error/404.html” /type “deny”    

You can use acs commons dispatcher flush to make a flush request(invalidate/delete) for the path on dispatcher  https://adobe-consulting-services.github.io/acs-aem-commons/features/dispatcher-flush-ui/index.html

Yes, you can manually configure the brand portal with aem on lower environment by following the above mentioned Adobe documents. I did manually condition last year with my stage environment but you need a separate instance of brand portal for another environment. It’s a 1:1 configuration 

private final AemContext context = AppAemContext.newAemContext(); private TestClass hello; private Page page;private Resource resource; @BeforeEachpublic void setup() throws Exception { // prepare a page with a test resourcepage = context.create().page("/content/mypage");resource = context.create()....

I am able to build and deploy AEM maven project with aem-uber jar 6.5.19 without any issue after upgradimg AEM to 6.5.19 with java 8 1) uber jar depenedency <!-- Adobe AEM Dependencies --><dependency><groupId>com.adobe.aem</groupId><artifactId>uber-jar</artifactId><version>6.5.19</version><scope>pro...

Ok it seems mockito 5.0.0 and above are not compatible with jdk 8. If you are using jdk can you try mockito4.9.0 and see if it gets resolved?

The above error shows that mockito-inline:5.8.0 is not present in the repository. Check on https://repo.maven.apache.org/maven2. It seems latest version there is 5.2.0. Try with that one.you can’t browse repo.abobe.com so try with some lower version to check if it downloads. Hope that helps