Dokumentation

Fehler: BUILD_MAVEN_PACKAGE_ERROR in AEM Cloud Manager

Last update: Wed Jul 03 2024 00:00:00 GMT+0000 (Coordinated Universal Time)

Wenn Sie auf eine Build_Maven_Package_Error in Adobe Experience Manager Cloud Manager ist dies auf einen Code-Fehler zurückzuführen. Dies kann durch Aktualisieren der Knotenversion in einem fehlerhaften Modul mithilfe von npm (Node Package Manager) behoben werden.

Beschreibung description

Umgebung

Adobe Experience Manager Cloud Manager

Problem/Symptome

Beheben des Fehlers - 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]

FEHLER im 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)

Auflösung resolution

Dieser Fehler ist auf ein Code-Problem zurückzuführen, das behoben werden muss, indem die Knotenversion in einem fehlerhaften Modul mit npm aktualisiert wird. Gehen Sie wie folgt vor, um diese Änderung vorzunehmen:

  1. Ermitteln der Knotenversion, die im Reaktor verwendet wird pom.xml. Beispiel unten = 16.14.0 pom.xml:

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

  2. Fügen Sie diese Knotenversion als devDependencies in die Datei package.json des Moduls ein, das nicht erstellt werden konnte. Im obigen Beispiel ist es UI Frontend.

    VORHER - 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