Hi Vani, Check other rules you have in your bundle's pom, make sure scope is right, given all good IntelliJ should not show it as unresolved. Regards,Peter

Hi Vani, Make sure to update your core pom to include assetshare,  <groupId>com.adobe.aem.commons</groupId> <artifactId>assetshare.core</artifactId> Regards,Peter

H Srini, Please see document below[1] [1] https://experienceleague.adobe.com/docs/experience-manager-65/deploying/configuring/configuring-performance.html?lang=en Regards,Peter

Hi Mahajan, There's nothing wrong with CONSOLE appender it's OOTB appender, when it gets triggered it means other configs for logs got messed up. Take backup of your instance,Open system console on slinglog page and compare your misconfigured log state with the OOTB instance config.Once you identify...

Hi Gaurav, Great discussion. There's no one rule fit's all here. It all depends on the use case and tech stack you have. Preparing right url's upfront in AEM is a great beginning, to avoid any redirects in first place. Routing to correct url's via Apache is a solid way to go on from here. Where Apac...

Hi Tarini, Yes, that's one way to solve it, Just keep the Service that know's it's state just a boolean, which is updated by the Job, so that it's near instant to know the state. Regards,Peter

Hi Tasunil, Expose API's to communicate clearly the status of the process. So that in case of a long running job you would be able to come back and check for status every few seconds.. This way you avoid long wait and have short nice calls into your core Job/Service connected to it. Regards,Peter

Hey Kent, If you are looking for a particular subdomain you can set auth requirement in the specific vhost as well. Regards,Peter

Hi Anish, Not really, AEM works much friendlier with Target. For Google Optimize: You just inject a Google Optimize tag into the head of your website and then configure A/B testing using the standard Google Chrome Plugin for Google Optimize. Regards,Peter

Hi Jamie, You would need to play with how you want Lucene to analyse your query. Luckily latest Lucene thats embedded into AEM contains various language Stem Factories, For example Latvian: https://lucene.apache.org/core/8_0_0/analyzers-common/org/apache/lucene/analysis/lv/LatvianStemFilterFactory.h...