Hi @Rahul_Dubey I think you should go with Apache PDFBox library instead of Flying Saucer. I also faced similar issues with flying saucer. With Flying Saucer, you resolve one dependency and it throws another one at you.For Apache PDFBox, add below dependencies in your core pom.xml <!-- https://mvnre...

Yes @jainrupal2408 it applies to language copies as well. This is an action performed from Rollout Configuration while creating language copy. 

Hi @jainrupal2408 Experience Fragments supports localization only when Experience Fragment component added on page is part of template structure.(Reference Document) For the XF components added manually on page, you need to write a custom Rollout Action and add it in your Rollout Configuration used ...

@anasustic Yes, you can add any property in cq:htmlTag. It will be added as an attribute in the outer html tag of the component.e.g<?xml version="1.0" encoding="UTF-8"?> <jcr:root xmlns:cq="http://www.day.com/jcr/cq/1.0" xmlns:jcr="http://www.jcp.org/jcr/1.0" jcr:primaryType="cq:Component"...

Hi @s1101v You can achieve this by using filevault-package-maven-plugin. You need to add an all module and in its pom.xml, using filevault-package-maven-plugin, package your core bundle in all package.I tried it in my local and it builds code successfully.Attaching sample project here. It is created...

@Anilkumar9 You can also go with Foundation Validation which is a best practice while applying custom validations on dialog fields.https://blogs.perficient.com/2017/11/06/aem-touch-ui-dialog-validation-new-best-practice-use-foundation-validation/ 

Hi @sangrampatil111 Can you please post the entry for cq:panelTitle property in translation_rules.xml?This is how we are doing it and it works.<nodelist> <node path="/content"> <property name="cq:panelTitle" /> </node> </nodelist> 

Hi @monish_gavaliPlease check below link for exactly similar use case. You have to use full text search query but it needs to be tweaked slightly.https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/fulltext-in-query-doesn-t-work-for-partial-search-term/m-p/402524 

Hi @vineetham123Please refer below links to understand how sling resource resolution works.https://www.aemcq5tutorials.com/tutorials/sling-resource-resolution-aem/https://medium.com/@techzette2/sling-resource-resolution-aem-a72fabc07a59 

Hi @vkarthick,Did you try following things?Restarting AEM instanceUsing different version of the dependencyCheck the scope of the dependency. It has to be available at runtime as well. Try with scope "provided".Checking any other error in stack trace.