Issue with AEM 6.6.0 Uber Jar During Upgrade to 6.5 LTS | Community
Skip to main content
J
jooca
Level 2
August 19, 2025
Solved

Issue with AEM 6.6.0 Uber Jar During Upgrade to 6.5 LTS

  • August 19, 2025
  • 2 replies
  • 1128 views

Hi Folks,

I’m facing an issue while upgrading our AEM environment from 6.5.21 to 6.5 LTS. As part of the upgrade, I updated the dependency in our pom.xml like below:

 

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

 

However, during the build process, I’m encountering the following error:

ZipException opening "uber-jar-6.6.0.jar": zip END header not found

Upon inspection, I noticed that the downloaded uber-jar-6.6.0.jar is only 2 KB in size, whereas the previous versions like 6.5.21 and 6.5.22 are around 62 MB and work without issues.

This suggests that the 6.6.0 Uber Jar might be corrupted or incomplete in the public Maven repository. Could you please confirm if this is a known issue then can anyone provide a valid solution for this? If possible kindly provide detailed steps.

Best answer by lukasz-m

Hi @jooca,

According to Adobe documentation AEM 6.5 LTS you have to use apis classifier in your pom every time you are including 6.6.0 uber-jar dependency in your project pom files.

It is because unlike in AEM 6.5, in LTS all public apis are now part of uber-jar-6.6.0-apis.jar not uber-jar-6.6.0.jar. This is why uber-jar-6.6.0.jar is so small, but this is correct, please check the size of uber-jar-6.6.0-apis.jar which you should use.

To solve your issue please make sure that:

  • in parent pom you have entry like this
    <dependency> <groupId>com.adobe.aem</groupId> <artifactId>uber-jar</artifactId> <version>6.6.0</version> <classifier>apis</classifier> <scope>provided</scope> </dependency>​
  • in all other maven modules with pom files, that inherits uber-jar version from root pom make sure to keep classifier tag, this will guarantee uber-jar-6.6.0-apis.jar is used
    <dependency> <groupId>com.adobe.aem</groupId> <artifactId>uber-jar</artifactId> <classifier>apis</classifier> </dependency>

So uber-jar is not corrupted, and all artifacts you can find in maven repository are fine. The main case is to use uber-jar-6.6.0-apis.jar instead of uber-jar-6.6.0.jar.

2 replies

MukeshYadav_
Community Advisor
MukeshYadav_Community Advisor
Community Advisor
August 19, 2025

Hi @jooca ,
Ensure jar file is not corrupted, try after re-downloading.

Some times we get this error with specific java version.
You may try with different supported Java version.
Thanks

    lukasz-m
    Community Advisor
    lukasz-mCommunity AdvisorAccepted solution
    Community Advisor
    August 19, 2025

    Hi @jooca,

    According to Adobe documentation AEM 6.5 LTS you have to use apis classifier in your pom every time you are including 6.6.0 uber-jar dependency in your project pom files.

    It is because unlike in AEM 6.5, in LTS all public apis are now part of uber-jar-6.6.0-apis.jar not uber-jar-6.6.0.jar. This is why uber-jar-6.6.0.jar is so small, but this is correct, please check the size of uber-jar-6.6.0-apis.jar which you should use.

    To solve your issue please make sure that:

    • in parent pom you have entry like this
      <dependency> <groupId>com.adobe.aem</groupId> <artifactId>uber-jar</artifactId> <version>6.6.0</version> <classifier>apis</classifier> <scope>provided</scope> </dependency>​
    • in all other maven modules with pom files, that inherits uber-jar version from root pom make sure to keep classifier tag, this will guarantee uber-jar-6.6.0-apis.jar is used
      <dependency> <groupId>com.adobe.aem</groupId> <artifactId>uber-jar</artifactId> <classifier>apis</classifier> </dependency>

    So uber-jar is not corrupted, and all artifacts you can find in maven repository are fine. The main case is to use uber-jar-6.6.0-apis.jar instead of uber-jar-6.6.0.jar.

      Uppari_Ramesh
      Uppari_Ramesh
      Level 5
      August 20, 2025

      @lukasz-m You are absolutely right!! We should shoue apis jar.

        Terms & ConditionsAccessibility statement

        Loading footer...