Hi @sreenu539,All models located under internal package are not exported by core components bundles. This means you cannot use them directly, this is done by design.The proper way to extend Core Components model is to use delegation pattern. Here you can find some information with examples:https://experienceleague.adobe.com/docs/experience-manager-core-components/using/developing/customizing.html?lang=en#customizing-the-logic-of-a-core-componenthttps://github.com/adobe/aem-core-wcm-components/wi...

Hi @Vani1012,It is possible to add Asset Share Commons 1.9.4 to existing project generated from Adobe AEM archetype using command from your post. All steps are described under https://opensource.adobe.com/asset-share-commons/pages/development/1-x/guide/I was able to successfully setup new AEM project with Asset Share Commons 1.9.4, base on above article.

I was able to successfully build project using commands you have shared and follow instructions presented in the official guide. I can see that your pom has some additional entries that are not included in the guide.Base on the documentation I would expect that content-package-maven-plugin section in ui.apps module will look like this com.day.jcr.vault content-package-maven-plugin true true true com.adobe.aem.commons assetshare.ui.apps true I am not sure why you have added additional entri...

Hi @adisharm,You can configure Persisted GraphQL queries - all the details about this approach you can find under official Adobe tutorial/documentation - https://experienceleague.adobe.com/docs/experience-manager-learn/getting-started-with-aem-headless/graphql/advanced-tutorial/graphql-persisted-queries.html?lang=en

Hi @Vani1012,In general the fact that 1.9.4 contains dependency to uberjar 6.3.1 should not be an issue, according to official documentation 1.9.4 is compatible with AEM 6.5. You can also switch to version 2.x but please be aware that those version are not including uberjar 6.5.x anyway.I am not sure how you wanted to approach with extending Asset Share Commons. But if you have planned to checkout the code and change it, then this will be incorrect way. Any customization should be done via API e...

Hi @srinivas_chann1,TagManager.find method will generate XPath query like below - it can be a bit different depending on basePath and list of tags. In this example following input has been used:basePath = /contenttagIDs = we-retail:activity/hiking, we-retail:activity/biking/jcr:root/content//element(*, cq:Taggable)[ (@cq:tags = 'we-retail:activity/hiking' or @cq:tags = '/content/cq:tags/we-retail/activity/hiking') and (@cq:tags = 'we-retail:activity/biking' or @cq:tags = '/content/cq:tags/we-ret...