Premkarthic​ AEM-6.2-Communities-LiveFyre-Feature-Pack-3 is this one:https://www.adobeaemcloud.com/content/marketplace/marketplaceProxy.html?packagePath=/content/companies/public/adobe/pack… In the details tab of package share, you'll see that it is version 1.10.167. You should also be able to locate that same version of the communities package in package manager of your AEM instance. Declare the build dependencies in the pom using the same version as follows:com.adobe.cq.socialcq-socialcommunit...

What version of AEM are you using and what version of cq-socialcommunities-pkg is installed in it? the api jar needs to match the pkg version. api 1.9.236 and console 1.3.0 are not compatible.

Here is the relevant documentation link:Using Maven for Communities

This is not correct - do not use individual communities jars in your dependency list since they are not available in public repos. JK Kendall's advice is correct - use only the cq-socialcommunities-api jar that corresponds to the communities-pkg installed in AEM, and place it just before the AEM uber jar in the dependency list in the pom. Then post your full build log here if you're still having problems.

Are you using AEM Communities 6.1 or later? If yes, this is similar to near-term roadmap features, and it would be worth contacting your sales representative to engage in the featurepack process.

This should be available now. Sorry for the delayDon

@brumoona87688495 if you have Communities FP5 or later installed, we've discovered an incompatibility. Please see this suggestion:http://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/adobe-experience-manager.topic.forum__98y7-im_having_troublere__kcrx-hi_weveconfirmed._s_1_tosp.html/forum__98y7-im_having_troublere.html#forum__98y7-im_having_troublere__kcrx-hi_weveconfirmedIf you do not have a Communities feature pack installed then the problem may be different and that so...