AEM Dependency Jars Not Available

[brett_birschbac]

I am seeing discrepancies with instructions for "How-To Work with JSPs” @ http://docs.adobe.com/docs/en/aem/6-1/develop/dev-tools/ht-projects-maven.html.  The instructions state that I need to add all of the dependency libraries in the "Adding Tag Library Dependencies" section, which references the "How-To Add Dependencies" section.

In summary:
- I cant pull the individual dependencies from https://repo.adobe.com/nexus/content/groups/public/ because it doesnt have the latest artifact versions
- I cant build JSPs using the uber-jar from https://repo.adobe.com/nexus/content/groups/public/com/adobe/aem/uber-jar/6.1.0/ because it is obfuscated

===================

Details:
The issue I am seeing is that there are cases where the AEM Dependency Manager is showing a dependency on a library version that does not exist on Adobe’s maven repo @ https://repo.adobe.com/nexus/content/groups/public/.

For instance, if I search for “com.day.cq.wcm.core.components” on AEM 6.1, it tells me I need the following dependency:
 

<dependency> <groupId>com.day.cq.wcm</groupId> <artifactId>cq-wcm-core</artifactId> <version>5.8.200</version> <scope>provided</scope> </dependency>

However, if I go out to https://repo.adobe.com/nexus/content/groups/public/com/day/cq/wcm/cq-wcm-core/ the latest available version is 5.7.10.

As an alternative to including the individual dependencies, I tried using the "uber-jar" dependency:

<dependency> <groupId>com.adobe.aem</groupId> <artifactId>uber-jar</artifactId> <version>6.1.0</version> <classifier>obfuscated-apis</classifier> <scope>provided</scope> </dependency>

     
However, because the jar is obfuscated, I get errors when compiling JSPs, such as "Failed to execute goal org.apache.sling:maven-jspc-plugin:2.0.6:jspc (compile-jsp) on project fmmp-base-content: Execution compile-jsp of goal org.apache.sling:maven-jspc-plugin:2.0.6:jspc failed: An API incompatibility was encountered while executing org.apache.sling:maven-jspc-plugin:2.0.6:jspc: java.lang.VerifyError: (class: com/day/cq/wcm/tags/DefineObjectsTEI, method: <init> signature: ()V) Constructor must call super() or this()"

Please advise.

[smacdonald2008]

I have asked support if this is a known issue. If 6.1 dependencies are not in the Adobe Mave Repo - this is an issue. 

[Sham_HC]

File support request with sample project to reproduce issue inhouse.

[smacdonald2008]

You are correct - i was able to duplicate this issue. Using the 6.1 Dependecny Finder - it stated i required:

 <dependency>
    <groupId>com.day.cq.wcm</groupId>
    <artifactId>cq-wcm-core</artifactId>
    <version>5.8.200</version>
    <scope>provided</scope>
</dependency>

But i got an error in my Maven build when i referenced this.

[Lokesh_Shivalingaiah]

There are many such dependency versions missing !!

[smacdonald2008]

This looks like a bug

[brett_birschbac]

Indeed.  It looks like most of the individual jars stopped posting versions to the Adobe Maven Repo sometime in 2013.

[smacdonald2008 · Accepted solution]

Open a ticket here:

https://helpx.adobe.com/marketing-cloud/contact-support.html

In mean time - check out this:

https://github.com/justinedelson/aem-uberjar-demo

[JK_Kendall]

A similar discussion is JAR not available at adobe repositories

You do have to make a request to Support to obtain the full jar.

- JK

[brett_birschbac]

I have a support request in with Day Care, so we will see where it goes from there.

[ramya_reddy]

Hi,

I am facing similar issue with including dependency for com.adobe.cq.projects.api(version 0.2.2) for AEM 6.3. I am using Uber jar with obfuscated-apis. Will including unobfuscated uber jar fix this issue?

Thanks,

Ramya

[Lokesh_Shivalingaiah]

You can try with the unobfuscated version or raise a support ticket

On Tue, Oct 17, 2017 at 12:20 PM, ramya.reddy <forums_noreply@adobe.com>

[ramya_reddy]

My issue is resolved after I used unobfuscated version of Uber jar. Thanks!