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

Have you defined vault.user and vault.password in your parent Pom.xml which should be same as your aem credentials and if it’s done and install is still failing with maven command try adding <useProxy>false</useProxy> for content-package-maven-plugin in your main Pom.xml

You need to update the Uber jar dependency as <dependency><groupId>com.adobe.aem</groupId><artifactId>uber-jar</artifactId><version>6.5.19</version><scope>provided</scope></dependency> now there is no classifier as explained on https://experienceleague.adobe.com/docs/experience-manager-65/content/re...

Only applying create, modify, and delete permissions on the /conf folder should work. I created a test user with above permission and adding dam user group default aem OOTB to the the test user and was able to edit existing the metadata and also able to create a new metadata schema. Check the group ...

2 gb is the minimum requirement for aem to start. Memory consumption depends on how large your repo is. However you can check on below points. 1) any custom index deployed on aem  2) is dispatcher is doing the caching for most of the content. Dispatcher cache hit ratio more than 95% is considered go...