AEM 6.0 upgrade to AEM 6.2 - com.adobe.cq.social.cq-social-blog Removed
Hello,
I am in the process of upgrading my AEM 6.0 instance to AEM 6.2. We have a rather large blog that utilizes the cq-social-blog (com.adobe.cq.social.cq-social-blog). I realize that the social blog was deprecated in AEM 6.1 and completely removed in AEM 6.2. I need this functionality back for AEM 6.2. I tried to include the dependency in the POM files but I am getting some rather strange errors that I am not able figure out.
Here is what I included in the parent POM:
<dependency> <groupId>com.adobe.acs</groupId> <artifactId>acs-aem-commons-bundle</artifactId> <version>3.3.0</version> <scope>provided</scope> </dependency> <dependency> <groupId>com.adobe.cq.social</groupId> <artifactId>cq-social-blog</artifactId> <version>1.0.15</version> </dependency> <dependency> <groupId>com.adobe.cq.social</groupId> <artifactId>cq-social-storage</artifactId> <version>1.0.0</version> </dependency>
And here is what I am including the in the bundle POMs:
<dependency> <groupId>com.adobe.aem</groupId> <artifactId>uber-jar</artifactId> <classifier>apis</classifier> </dependency> <dependency> <groupId>com.adobe.cq.social</groupId> <artifactId>cq-social-blog</artifactId> </dependency> <dependency> <groupId>com.adobe.cq.social</groupId> <artifactId>cq-social-storage</artifactId> </dependency>
Here is the exception I am getting, which from doing research, sounds like a dependency issue:
02.11.2016 13:52:56.500 *ERROR* [0:0:0:0:0:0:0:1 [1478112776389] GET /content/sites/foo/blog.html HTTP/1.1] org.apache.sling.servlets.resolver.internal.SlingServletResolver Original error class java.lang.LinkageError
java.lang.LinkageError: loader constraint violation: loader (instance of org/apache/felix/framework/BundleWiringImpl$BundleClassLoaderJava5) previously initiated loading for a different type with name "com/adobe/cq/social/blog/BlogManager"
This exception is occurring when I try to get a Blog object from a BlogManager object. Any help porting over the cq-social-blog in AEM 6.2 in much appreciated.
PS: I realize that the blog has been replaced with the new 'Journals' feature, but my team and I do not have capacity at this point in time to convert the existing AEM 6.0 blog to journals.