Documentation

Error: BUILD_MAVEN_PACKAGE_ERROR in AEM Cloud Manager

Last update: Tue Jul 23 2024 00:00:00 GMT+0000 (Coordinated Universal Time)

Whenever you encounter a Build_Maven_Package_Error in Adobe Experience Manager Cloud Manager, it is due to a code failure. This can be resolved by updating the node version in a failed module using npm (Node Package Manager).

Description description

Environment

Adobe Experience Manager Cloud Manager

Issue/Symptoms

How to resolve the error - Build_Maven_Package_Error in AEM Cloud Manager?

19:19:53,214 [ main]  [ INFO]  ------------------------------------------------------------------------

    19:19:53,215 [ main]  [ INFO]  Reactor Summary for customer_name XXXX.XXX.XXXXXXX.XXXXXXXXXX:{}:

    19:19:53,215 [ main]  [ INFO]

    19:19:53,216 [ main]  [ INFO]  customer_name ...................................... SUCCESS [   3.600 s]

    19:19:53,217 [ main]  [ INFO]  customer_name - Core ............................... SUCCESS [  17.855 s]

    19:19:53,218 [ main]  [ INFO]  customer_name - UI Frontend ........................ FAILURE [ 01:16 min]

    19:19:53,218 [ main]  [ INFO]  customer_name – UI React ........................... SKIPPED

    19:19:53,218 [ main]  [ INFO]  customer_name - UI apps ............................ SKIPPED

    19:19:53,219 [ main]  [ INFO]  customer_name - UI content ......................... SKIPPED

    19:19:53,219 [ main]  [ INFO]  customer_name Project Package ...................... SKIPPED

    19:19:53,219 [ main]  [ INFO]  customer_name - Dispatcher ......................... SKIPPED

    19:19:53,220 [ main]  [ INFO]  ------------------------------------------------------------------------

    19:19:53,220 [ main]  [ INFO]  BUILD FAILURE

    19:19:53,220 [ main]  [ INFO]  ------------------------------------------------------------------------

    19:19:53,222 [ main]  [ INFO]  Total time:  01:41 min

    19:19:53,224 [ main]  [ INFO]  Finished at: 2023-02-07T19:19:53Z

    19:19:53,224 [ main]  [ INFO]  ------------------------------------------------------------------------

    19:19:53,226 [ main]  [ ERROR]  Failed to execute goal com.github.xxxxx:frontend-maven-plugin:1.7.6:npm (npm run prod) on project com.xyz.ui.frontend: Failed to run task: 'npm run prod' failed. org.apache.commons.exec.ExecuteException: Process exited with an error: 2 (Exit value: 2) ->[ Help 1]

    19:19:53,227 [ main]  [ ERROR]

ERROR in P2 ticket:

Pipeline Name: Production Pipeline

    Pipeline Status: FAILED

    Failure Caused By: CUSTOMER

    Failed Step: build

    Error Message: org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1)

Resolution resolution

This failure is due to a code issue that needs to be resolved by updating the node version in a failed module using npm. To make this change, follow these steps:

  1. Find the node version that is being used in reactor pom.xml. Below example = 16.14.0 pom.xml:

    code language-none 
    <configuration>
        <nodeVersion>v16.14.0</nodeVersion>.
        <npmVersion>8.3.1</npmVersion>
    <configuration>

  2. Add this node version as devDependencies in the package.json file of the module that failed to build. In the above example, it is UI Frontend.

    BEFORE - package.json:

    code language-none 
    "devDependencies": {
    "@babel/core": "7.0.0",
    "@babel/plugin-proposal-class-properties": "7.3.3",
    "@babel/plugin-proposal-object-rest-spread": "7.3.2",
    "@material/tab-bar": "12.0.0",
    },

    AFTER - package.json:

    code language-none 
    "devDependencies": {
    "@types/node": "16.14.0",                          THIS LINE WAS ADDED
    "@babel/core": "7.0.0",
    "@babel/plugin-proposal-class-properties": "7.3.3",
    "@babel/plugin-proposal-object-rest-spread": "7.3.2",
    "@material/tab-bar": "12.0.0",
    },
recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f