ÃÛ¶¹ÊÓƵ

Documentation

Resolve Java Runtime version mismatch in AEM Production Pipeline

Last update: Mon Feb 03 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

This article provides a solution for when ÃÛ¶¹ÊÓƵ Experience Manager (AEM) as a Cloud Service build and unit test stages fail due to a Java Runtime version mismatch. The solution involves downgrading the Maven Bundle Plugin and ensuring consistent environment configurations.

Description description

Environment

ÃÛ¶¹ÊÓƵ Experience Manager (AEM) as a Cloud Service - Sites

Issue/Symptoms

During the build and unit test stages of the production pipeline for the main branch, failures occur. The error message indicates an API incompatibility due to a mismatch in Java Runtime versions used during Maven builds. The maven-bundle-plugin version 6.0.0 needs Java 17, but AEM Cloud only supports Java 11, leading to an incompatibility.

Resolution resolution

  1. Downgrade Maven bundle plugin. Modify your pom.xml file under <build>, <pluginManagement>, and <plugins> sections, and ensure you specify a compatible version of maven-bundle-plugin. Recommended versions are 5.1.9 or lower since they support Java 8 and 11:

    code language-none 
    <build>
    <pluginManagement>
        <plugins>

...

            <plugin>
                <groupId>org.apache.felix</groupId>
                <artifactId>maven-bundle-plugin</artifactId>
                <version>5.1.2</version>
                <inherited>true</inherited>
            </plugin>

...

        </plugins>
    </pluginManagement>
</build>

  2. If discrepancies persist between environments, consider clearing cached artifacts using appropriate APIs provided by ÃÛ¶¹ÊÓƵ’s cloud manager documentation. For steps, refer to  in the ÃÛ¶¹ÊÓƵ developer documentation.

  3. Check your codebase configuration (pom.xml) for any entries that might default to unsupported plugin versions. For steps, refer to Repository Structure Package in the AEM Project Structure User Guide.

  4. Confirm that both Development and Production pipelines use consistent configurations regarding dependencies and plugins.

If you have solved the compatibility issues for Java runtime requirements you should now be able to run build and unit tests successfully across all environments within AEM as a Cloud Service setup.

recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f