Resolving Java Version Conflicts in AEM Builds

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

Introduction

Adobe Experience Manager (AEM) builds can sometimes fail due to Java version conflicts. In this article, we will explore a common issue where the aQute/bnd/osgi/Analyzer has been compiled by a more recent version of the Java Runtime, causing build failures.

Understanding the Error

The error message indicates that the aQute/bnd/osgi/Analyzer has been compiled by a more recent version of the Java Runtime (class file version 61.0), which is not compatible with the current Java Runtime version (up to 55.0). This issue can occur when using Cloud Manager or building locally.

Causes of the Error

The error can be caused by:

• Using an outdated maven-bundle-plugin version that is not compatible with the current Java Runtime version.
• Not specifying the correct Java version in the pom.xml file or settings.xml file.

Solutions

Solution 1: Update maven-bundle-plugin Version

To resolve the issue, update the maven-bundle-plugin version to 5.1.9 or lower in the parent pom.xml file:

<plugin>
    <groupId>org.apache.felix</groupId>
    <artifactId>maven-bundle-plugin</artifactId>
    <version>5.1.4</version>
    <extensions>true</extensions>
    <configuration>
        <instructions>
            <Bundle-SymbolicName>com.xxx.xxx</Bundle-SymbolicName>
            <Sling-Model-Packages>
                com.xxxx.models
            </Sling-Model-Packages>
            <!-- <Embed-Dependency>json|nimbus-jose-jwt|tink;scope=compile;inline=true</Embed-Dependency> -->
            <Embed-Dependency>json</Embed-Dependency>
        </instructions>
    </configuration>
</plugin>

Solution 2: Specify Java Version in pom.xml File

Alternatively, specify the correct Java version in the pom.xml file:

<properties>
    <maven.compiler.source>11</maven.compiler.source>
    <maven.compiler.target>11</maven.compiler.target>
</properties>

Solution 3: Use Maven Tool Chain Plugin

If building with Cloud Manager, use the Maven Tool Chain plugin to specify the Java version:

<plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-toolchains-plugin</artifactId>
    <version>3.0.0</version>
    <configuration>
        <toolchains>
            <jdk>
                <version>11</version>
            </jdk>
        </toolchains>
    </configuration>
</plugin>

Conclusion

Resolving Java version conflicts in AEM builds requires careful attention to the maven-bundle-plugin version, Java version specification in pom.xml files, and the use of the Maven Tool Chain plugin. By following these solutions, you can ensure successful builds and avoid errors caused by Java version incompatibilities.

Related Articles

• AEM 6.5 and Java 17
• Maven Bundle Plugin
• Adobe Experience Manager Documentation