Yes, we did. The error remains exactly the same

We have to upgrade the mockito version to atleast 3.4 or any higher. However the moment we upgrade it all test cases start breaking : Page page = aemContext.create().page("/content/testPage"); with error  java.lang.IllegalArgumentException: Illegal page name.   This is what our pom looks like after ...

The bundleContext reference is part of static method, and mockito 3.3 doesnt allow mocking of static methods. Any higher version of mockito is not compatible with aemContext.   Can you elaborate more please, it will help us.

We have a common Utility class, which has following method  public static ResourceResolver getServiceResourceResolver(String subServiceName){        final BundleContext bundleContext = FrameworkUtil.getBundle(Util.class).getBundleContext();       final ServiceReference factoryReference = bundleConte...

We want to remote push to  AEM cloud repo

We do not want to set up automated sync for this particular branch on Cloud, and this has to be updated only after specific sign-offs hence needs to be manual via command.Any idea what could be going wrong here while we are trying to sync via git command

Is it possible to remote push from Git repo to Cloud repo, if the branch names are not same. Want to push from GIT to CLOUD repoGit repo branch name :- developCloud repo branch name :- uat Tried using git push https://git.cloudmanager.xxx.com/XXXX develop:uat Error :-(non-fast-forward)error: failed ...

We have a global deny rule on dispatcher /0001 { /type "deny" /glob "*" } and have allowed specific POST requests via rules like  { /type "allow" /url "POST /content/[.]*.form.html" }  #Example rule However, on publishers an autodiscover request is landingPOST /content/mySite/AutoDiscover/autodiscov...

@arunpatidar  Any issues on top of your mind which might arise if we add a deny rule for this request on dispatcher level?

any request for autodiscover.xml is not part of our custom code