Could not build the social-ugcbase1.1.34 bundle as it is depending on social-communities-api 1.1.34 version bundle

[#1]

~Hi All,

      I am trying to build our migration project through Maven. I added dependencies required.

When  i tried to build and install i got an error saying

[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project usgboral-bundle: Could not resolve dependencies for project melbourne-it:usgboral-bundle:bundle:3.0-USG-BORAL-SNAPSHOT: Failed to collect dependencies at com.adobe.cq.social:cq-s
ocial-ugcbase:jar:1.1.34: Failed to read artifact descriptor for com.adobe.cq.social:cq-social-ugcbase:jar:1.1.34: Could not find artifact com.adobe.cq.social:socialcommunities-parent:pom:1.1.34 in adobe (http://repo.ado
be.com/nexus/content/groups/public/) -> [Help 1]
[ERROR]

I thought of downloading the jars manually.But the required com.adobe.cq.social:socialcommunities-parent:pom:1.1.34  version does not exist.  Attaching the screenshot of the same.

The social-ugcbase-1.1.34 jar is dependent on social-communities-api-1.3.4 jar.

Please help me on this!!

Thanks,

maven-build-issue.PNG ‏53 KB

[#2]

Hi Kalyan,

Have you got any fix for this? We are trying to use 'com.adobe.cq.social.commons.client.api.ClientUtilities' in our code and this looks for ugcbase jar, however, whenever I add this jar and take the build, it gives me the same error which you mentioned. Any fix or solution for this?

Any pointers will be helpful.

Thanks

~Jay

[#3]

kunal23 wrote...

You need to refactor your communities code as in 6.1 many of the communities java api packages were reorganized. Did you follow the documentation for upgrading the communities - https://docs.adobe.com/docs/en/aem/6-1/deploy/communities/upgrade.html

Also, the links I shared with you earlier please go through this again - 

[1] https://docs.adobe.com/docs/en/aem/6-1/develop/communities/code-guide/maven.html

...

... what they said ...

Only the Communities API jar should be included.  

Inclusion of individual Communities jars is not supported.

For some info regarding the refactoring, see SocialUtils Refactoring.

- JK

[#4]

If you are still facing this issue I would recommend you to include the following dependencies in your pom.

            <dependency>

                <groupId>com.adobe.cq.social</groupId>

                <artifactId>cq-social-commons</artifactId>

                <version>1.5.103</version>

            </dependency>

          <dependency>

                <groupId>com.adobe.cq.social</groupId>

                <artifactId>cq-socialcommunities-api</artifactId>

                <version>1.10.111</version>

                <scope>provided</scope>

           </dependency>

Also please make sure you have settings.xm in place i.e. .m2/ with correct adobe public repository configured there which should be like below :

       <profile>
                <id>adobe-public</id> 
                <activation> 
                    <activeByDefault>true</activeByDefault> 
                </activation> 
                <repositories> 
                  <repository> 
                    <id>adobe</id> 
                    <name>Nexus Proxy Repository</name> 
                    <url>http://repo.adobe.com/nexus/content/groups/public/</url> 
                    <layout>default</layout> 
                  </repository> 
                </repositories> 
                <pluginRepositories> 
                  <pluginRepository> 
                    <id>adobe</id> 
                    <name>Nexus Proxy Repository</name> 
                    <url>http://repo.adobe.com/nexus/content/groups/public/</url> 
                    <layout>default</layout> 
                  </pluginRepository> 
                </pluginRepositories> 
            </profile>

Thanks,

Samir

[#5]

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.