在 LoongArch64 (loong64) 龙芯 3B6000 如何编译 seata 分布式事务？

xuxiaowei · July 28, 2026, 8:42pm

复现环境

在龙芯系统创建 Maven、JDK 25 容器，用于快速复现

docker run -itd --name seata-build registry.cn-qingdao.aliyuncs.com/kubernetesloong64/maven-loong64:3.9.16-25-debian-slim-git

docker exec -it seata-build bash

mvn -v

root@88e40ffc5856:/workspace# mvn -v
Apache Maven 3.9.16 (2bdd9fddda4b155ebf8000e807eb73fd829a51d5)
Maven home: /opt/maven
Java version: 25.0.3, vendor: Loongson, runtime: /opt/java/openjdk-25
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "7.1.3+deb14-loong64", arch: "loongarch64", family: "unix"
root@88e40ffc5856:/workspace#

修复已知问题

github.com/apache/incubator-seata

Unify protobuf and gRPC version properties into build/pom.xml and reference them via ${} instead of hardcoding versions

已打开 03:24AM - 24 Jul 26 UTC

已关闭 09:36AM - 25 Jul 26 UTC

xuxiaowei-com-cn

### Check Ahead - [x] I have searched the [issues](https://github.com/seata/sea…ta/issues) of this repository and believe that this is not a duplicate. - [x] I am willing to try to fix this bug myself. ### Ⅰ. Issue Description When building Seata on the LoongArch architecture, the `protobuf-maven-plugin` is unable to resolve the `protoc-gen-grpc-java` executable. ### Ⅱ. Describe what happened ```shell [ERROR] Failed to execute goal org.xolstice.maven.plugins:protobuf-maven-plugin:0.6.1:test-compile-custom (default) on project seata-grpc: Unable to resolve artifact: Missing: [ERROR] ---------- [ERROR] 1) io.grpc:protoc-gen-grpc-java:exe:linux-loongarch_64:1.55.1 [ERROR] [ERROR] Try downloading the file manually from the project website. [ERROR] [ERROR] Then, install it using the command: [ERROR] mvn install:install-file -DgroupId=io.grpc -DartifactId=protoc-gen-grpc-java -Dversion=1.55.1 -Dclassifier=linux-loongarch_64 -Dpackaging=exe -Dfile=/path/to/file [ERROR] [ERROR] Alternatively, if you host your own repository you can deploy the file there: [ERROR] mvn deploy:deploy-file -DgroupId=io.grpc -DartifactId=protoc-gen-grpc-java -Dversion=1.55.1 -Dclassifier=linux-loongarch_64 -Dpackaging=exe -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] [ERROR] [ERROR] Path to dependency: [ERROR] 1) org.apache.seata:seata-grpc:jar:2.8.0-SNAPSHOT [ERROR] 2) io.grpc:protoc-gen-grpc-java:exe:linux-loongarch_64:1.55.1 [ERROR] [ERROR] ---------- [ERROR] 1 required artifact is missing. [ERROR] [ERROR] for artifact: [ERROR] org.apache.seata:seata-grpc:jar:2.8.0-SNAPSHOT ``` <img width="2092" height="1230" alt="Image" src="https://github.com/user-attachments/assets/7d0b943b-c5ab-42b9-96e5-a40b23336ef9" /> ### Ⅲ. Describe what you expected to happen Seata should build successfully on the LoongArch architecture, or it should be possible to work around this issue by specifying protobuf/gRPC version parameters to use lower versions (such as protobuf 3.25.4 and gRPC 1.54.2) available in the LoongArch Maven repository. ### Ⅳ. How to reproduce it (as minimally and precisely as possible) 1. Clone the Seata repository on a LoongArch machine 2. Run `mvn clean package` 3. The build fails at the `seata-grpc` module **Root Cause Analysis:** 1. The Maven Central repository does not contain the `protoc-gen-grpc-java` executable for the LoongArch architecture 2. The LoongArch Maven repository (https://maven.loongnix.cn/loongarch/maven/) has `io.grpc:protoc-gen-grpc-java` up to version 1.54.2 only, which does not meet the required version 1.55.1 3. The version numbers `3.25.4` (protobuf) and `1.55.1` (gRPC) are hardcoded in multiple places in the code: ``` ./core/pom.xml: com.google.protobuf:protoc:3.25.4:exe:${os.detected.classifier} ./test-suite/test-new-version/pom.xml: com.google.protobuf:protoc:3.25.4:exe:${os.detected.classifier} ./test-suite/test-new-version/pom.xml: io.grpc:protoc-gen-grpc-java:1.55.1:exe:${os.detected.classifier} ./serializer/seata-serializer-protobuf/pom.xml: com.google.protobuf:protoc:3.25.4:exe:${os.detected.classifier} ./dependencies/pom.xml: <protobuf.version>3.25.5</protobuf.version> ./dependencies/pom.xml: <grpc.version>1.55.1</grpc.version> ./extensions/rpc/seata-grpc/pom.xml: com.google.protobuf:protoc:3.25.4:exe:${os.detected.classifier} ./extensions/rpc/seata-grpc/pom.xml: <pluginArtifact>io.grpc:protoc-gen-grpc-java:1.55.1:exe:${os.detected.classifier}</pluginArtifact> ``` <img width="1448" height="146" alt="Image" src="https://github.com/user-attachments/assets/f2ec49dd-3826-4704-a666-818cc34b06d2" /> 4. `<protobuf.version>3.25.5</protobuf.version>` and `<grpc.version>1.55.1</grpc.version>` are defined in `./dependencies/pom.xml`, but there is no parent-child relationship between it and `./extensions/rpc/seata-grpc/pom.xml` (or other sub-modules), so `${protobuf.version}` and `${grpc.version}` cannot be resolved in the `seata-grpc` module and other sub-modules 5. Attempting to downgrade the build with `mvn clean package -Dgrpc.version=1.54.2` still results in `${protobuf.version}` and `${grpc.version}` being unresolvable, with the error: ``` Downloading from nexus-settings: .../io/grpc/protoc-gen-grpc-java/$%7Bgrpc.version%7D/protoc-gen-grpc-java-$%7Bgrpc.version%7D.pom ``` <img width="1644" height="91" alt="Image" src="https://github.com/user-attachments/assets/e4030c80-4a75-4b00-9f94-b57a16f38c28" /> **Root Cause:** The `<protobuf.version>` and `<grpc.version>` properties are defined in `./dependencies/pom.xml`, but this POM has no parent-child relationship with the `seata-grpc` module (their common parent is `org.apache.seata:seata-build`), so the properties cannot be inherited and used. ### Ⅴ. Anything else we need to know? _No response_ ### Ⅵ. Environment - Seata client/server version: 2.8.0-SNAPSHOT - OS: Linux (LoongArch)

github.com/apache/incubator-seata

Bug: The frontend-maven-plugin fails to use the -DnodeVersion property to override the Node version that will be downloaded

已打开 05:34PM - 28 Jul 26 UTC

已关闭 04:57AM - 08 Aug 26 UTC

xuxiaowei-com-cn

### Check Ahead - [x] I have searched the [issues](https://github.com/seata/sea…ta/issues) of this repository and believe that this is not a duplicate. - [x] I am willing to try to fix this bug myself. ### Ⅰ. Issue Description - Unable to use `-DnodeVersion` to modify the Node version number to be downloaded. ```xml <plugin> <groupId>com.github.eirslett</groupId> <artifactId>frontend-maven-plugin</artifactId> <configuration> <workingDirectory>src/main/resources/static/console-fe</workingDirectory> </configuration> <executions> <execution> <id>install node and npm</id> <goals> <goal>install-node-and-npm</goal> </goals> <phase>generate-resources</phase> <configuration> <nodeVersion>v19.5.0</nodeVersion> </configuration> </execution> </executions> </plugin> ``` ### Ⅱ. Describe what happened 1. While executing the compilation commands on a Loongson (LoongArch) computer, it was observed that the Node.js 19.5.0 release for the Loongson architecture is not available at https://unofficial-builds.nodejs.org/download/release/. ```shell mvn -V -T 1C package -pl console -am -DskipTests -Dgrpc.version=1.54.2 -DnodeDownloadRoot=https://unofficial-builds.nodejs.org/download/release/ ``` ```shell debian-14:/srv/java/incubator-seata# mvn -V -T 1C package -pl console -am -DskipTests -Dgrpc.version=1.54.2 -DnodeDownloadRoot=https://unofficial-builds.nodejs.org/download/release/ Apache Maven 3.9.16 (2bdd9fddda4b155ebf8000e807eb73fd829a51d5) Maven home: /srv/apache-maven-3.9.16 Java version: 25.0.3, vendor: Loongson, runtime: /srv/jdk-25.0.3 Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "7.1.3+deb14-loong64", arch: "loongarch64", family: "unix" [INFO] Scanning for projects... [INFO] ------------------------------------------------------------------------ [INFO] Detecting the operating system and CPU architecture [INFO] ------------------------------------------------------------------------ [INFO] os.detected.name: linux [INFO] os.detected.arch: loongarch_64 [INFO] os.detected.version: 7.1 [INFO] os.detected.version.major: 7 [INFO] os.detected.version.minor: 1 [INFO] os.detected.release: debian [INFO] os.detected.release.like.debian: true [INFO] os.detected.classifier: linux-loongarch_64 [INFO] ------------------------------------------------------------------------ [INFO] Reactor Build Order: [INFO] [INFO] Seata Build 2.8.0-SNAPSHOT [pom] [INFO] Seata Parent POM 2.8.0-SNAPSHOT [pom] [INFO] seata-common 2.8.0-SNAPSHOT [jar] [INFO] seata-console 2.8.0-SNAPSHOT [jar] [INFO] ...... [INFO] --- frontend:1.15.0:install-node-and-npm (install node and npm) @ seata-console --- [WARNING] Unable to determine current node version: org.apache.commons.exec.ExecuteException: Process exited with an error: 2 (Exit value: 2) [INFO] Installing node version v19.5.0 [INFO] Downloading https://unofficial-builds.nodejs.org/download/release/v19.5.0/node-v19.5.0-linux-loong64.tar.gz to /srv/apache-maven-repo/com/github/eirslett/node/19.5.0/node-19.5.0-linux-loong64.tar.gz [INFO] No proxies configured [INFO] No proxy was configured, downloading directly [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary for Seata Parent POM 2.8.0-SNAPSHOT 2.8.0-SNAPSHOT: [INFO] [INFO] Seata Build 2.8.0-SNAPSHOT ......................... SUCCESS [ 1.239 s] [INFO] Seata Parent POM 2.8.0-SNAPSHOT .................... SUCCESS [ 2.278 s] [INFO] seata-common 2.8.0-SNAPSHOT ........................ SUCCESS [ 1.650 s] [INFO] seata-console 2.8.0-SNAPSHOT ....................... FAILURE [ 2.766 s] [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 9.135 s (Wall Clock) [INFO] Finished at: 2026-07-29T01:09:21+08:00 [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.15.0:install-node-and-npm (install node and npm) on project seata-console: Could not download Node.js: Got error code 404 from the server. -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn <args> -rf :seata-console debian-14:/srv/java/incubator-seata# ``` 2. Although Node.js v20.20.2 is available at https://unofficial-builds.nodejs.org/download/release/ , we used the parameter `-DnodeVersion=v20.20.2` to specify that version, but found that the parameter was ignored and it still downloaded Node.js 19.5.0. ```shell mvn -V -T 1C package -pl console -am -DskipTests -Dgrpc.version=1.54.2 -DnodeDownloadRoot=https://unofficial-builds.nodejs.org/download/release/ -DnodeVersion=v20.20.2 ``` 3. After searching the source code, we found that the Node.js version is hardcoded. ```shell grep -r --include="pom.xml" -B 16 "19.5.0" . ``` ```shell debian-14:/srv/java/incubator-seata# grep -r --include="pom.xml" -B 16 "19.5.0" . ./console/pom.xml- <build> ./console/pom.xml- <plugins> ./console/pom.xml- <plugin> ./console/pom.xml- <groupId>com.github.eirslett</groupId> ./console/pom.xml- <artifactId>frontend-maven-plugin</artifactId> ./console/pom.xml- <configuration> ./console/pom.xml- <workingDirectory>src/main/resources/static/console-fe</workingDirectory> ./console/pom.xml- </configuration> ./console/pom.xml- <executions> ./console/pom.xml- <execution> ./console/pom.xml- <id>install node and npm</id> ./console/pom.xml- <goals> ./console/pom.xml- <goal>install-node-and-npm</goal> ./console/pom.xml- </goals> ./console/pom.xml- <phase>generate-resources</phase> ./console/pom.xml- <configuration> ./console/pom.xml: <nodeVersion>v19.5.0</nodeVersion> debian-14:/srv/java/incubator-seata# ``` ### Ⅲ. Describe what you expected to happen Supports using `-DnodeVersion=` to specify the Node.js version to be downloaded and used. ### Ⅳ. How to reproduce it (as minimally and precisely as possible) 1. Use `mvn -V -T 1C package -pl console -am -DskipTests -DnodeVersion=v20.20.2` to specify the Node.js version to be downloaded and used. 2. Run `./console/src/main/resources/static/console-fe/node/node -v` to check the Node version, and find that it is not the one you specified. ``` xuxiaowei@xiaomi  ~/IdeaProjects/github.com/xuxiaowei-com-cn/incubator-seata   2.x  ./console/src/main/resources/static/console-fe/node/node -v v19.5.0 xuxiaowei@xiaomi  ~/IdeaProjects/github.com/xuxiaowei-com-cn/incubator-seata   2.x  ``` ### Ⅴ. Anything else we need to know? ### Ⅵ. Environment - JDK：25 - This issue can be reproduced on any operating system.

第一次编译打包

命令

mvn -V -e package -DskipTests

问题

[INFO] ------------------------------------------------------------------------
[INFO] Detecting the operating system and CPU architecture
[INFO] ------------------------------------------------------------------------
[INFO] os.detected.name: linux
[INFO] os.detected.arch: unknown
[INFO] os.detected.version: 7.1
[INFO] os.detected.version.major: 7
[INFO] os.detected.version.minor: 1
[ERROR] unknown os.arch: loongarch64 -> [Help 1]
org.apache.maven.MavenExecutionException: unknown os.arch: loongarch64
    at kr.motd.maven.os.DetectExtension.afterProjectsRead (DetectExtension.java:95)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:223)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:919)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:285)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:207)
    at jdk.internal.reflect.DirectMethodHandleAccessor.invoke (DirectMethodHandleAccessor.java:104)
    at java.lang.reflect.Method.invoke (Method.java:565)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:255)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:201)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:362)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:314)
[ERROR] 
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MavenExecutionException

解决方案

在本地 Maven 仓库，删除不支持龙芯 CPU 的 kr.motd.maven:os-maven-plugin

rm -rf ~/.m2/repository/kr/motd/maven

root@3b92fe34a154:/workspace/incubator-seata# find ~/.m2/repository/kr/motd/maven
/root/.m2/repository/kr/motd/maven
/root/.m2/repository/kr/motd/maven/os-maven-plugin
/root/.m2/repository/kr/motd/maven/os-maven-plugin/1.5.0.Final
/root/.m2/repository/kr/motd/maven/os-maven-plugin/1.5.0.Final/_remote.repositories
/root/.m2/repository/kr/motd/maven/os-maven-plugin/1.5.0.Final/os-maven-plugin-1.5.0.Final.jar
/root/.m2/repository/kr/motd/maven/os-maven-plugin/1.5.0.Final/os-maven-plugin-1.5.0.Final.jar.sha1
/root/.m2/repository/kr/motd/maven/os-maven-plugin/1.5.0.Final/os-maven-plugin-1.5.0.Final.pom
/root/.m2/repository/kr/motd/maven/os-maven-plugin/1.5.0.Final/os-maven-plugin-1.5.0.Final.pom.sha1
root@3b92fe34a154:/workspace/incubator-seata# rm -rf ~/.m2/repository/kr/motd/maven
root@3b92fe34a154:/workspace/incubator-seata#

同时使用 https://maven.loongnix.cn/loongarch/maven 、https://maven.aliyun.com/repository/public Maven 仓库

优先级 https://maven.loongnix.cn/loongarch/maven > https://maven.aliyun.com/repository/public
无法在 settings.xml 中使用 <mirror>，因为 <mirror> 针对于中央仓库 <mirrorOf>central</mirrorOf> 只能使用一个仓库，无法同时使用多个仓库
需要在 settings.xml 中使用 <profiles>，才能同时启用多个仓库

settings.xml

创建默认 settings.xml 配置

使用 <profiles> 可以同时配置并启用多个仓库

首先使用 https://maven.loongnix.cn/loongarch/maven 仓库
如果 https://maven.loongnix.cn/loongarch/maven 仓库依赖不存在，再使用 https://maven.aliyun.com/repository/public 仓库
如果不按照上述顺序配置仓库，可能会遇见下载的依赖 kr.motd.maven:os-maven-plugin、com.github.eirslett:frontend-plugin-core、com.github.eirslett:frontend-maven-plugin 无法识别 CPU 类型。解决方案见：在 LoongArch64 (loong64) 龙芯 3B6000 如何编译 seata 分布式事务？ - #2，来自 xuxiaowei
因为要下载的依赖的仓库 id 都是默认的 central，所以必须在 settings.xml 使用 <profiles>
如果是不同的 id，可以在 settings.xml 使用 <mirror>

使用 <activeProfiles> 默认激活 <profiles>

mkdir -p ~/.m2

cat <<EOF | tee ~/.m2/settings.xml
<?xml version="1.0" encoding="UTF-8"?>
<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
          xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">

    <profiles>
        <profile>
            <id>loongarch</id>
            <repositories>
                <repository>
                    <id>loongarch</id>
                    <name>loongarch</name>
                    <url>https://maven.loongnix.cn/loongarch/maven</url>
                    <releases>
                        <enabled>true</enabled>
                    </releases>
                    <snapshots>
                        <enabled>false</enabled>
                    </snapshots>
                </repository>
                <repository>
                    <id>aliyun</id>
                    <name>aliyun</name>
                    <url>https://maven.aliyun.com/repository/public</url>
                    <releases>
                        <enabled>true</enabled>
                    </releases>
                    <snapshots>
                        <enabled>false</enabled>
                    </snapshots>
                </repository>
            </repositories>
            <pluginRepositories>
                <pluginRepository>
                    <id>loongarch</id>
                    <name>loongarch</name>
                    <url>https://maven.loongnix.cn/loongarch/maven</url>
                    <releases>
                        <enabled>true</enabled>
                    </releases>
                    <snapshots>
                        <enabled>false</enabled>
                    </snapshots>
                </pluginRepository>
                <pluginRepository>
                    <id>aliyun</id>
                    <name>aliyun</name>
                    <url>https://maven.aliyun.com/repository/public</url>
                    <releases>
                        <enabled>true</enabled>
                    </releases>
                    <snapshots>
                        <enabled>false</enabled>
                    </snapshots>
                </pluginRepository>
            </pluginRepositories>
        </profile>
    </profiles>

    <activeProfiles>
        <activeProfile>loongarch</activeProfile>
    </activeProfiles>
</settings>

EOF

第二次编译打包

命令

mvn -V clean package -DskipTests

问题

[ERROR] Failed to execute goal org.xolstice.maven.plugins:protobuf-maven-plugin:0.6.1:test-compile-custom (default) on project seata-grpc: Unable to resolve artifact: Missing:
[ERROR] ----------
[ERROR] 1) io.grpc:protoc-gen-grpc-java:exe:linux-loongarch_64:1.55.1
[ERROR] 
[ERROR]   Try downloading the file manually from the project website.
[ERROR] 
[ERROR]   Then, install it using the command: 
[ERROR]       mvn install:install-file -DgroupId=io.grpc -DartifactId=protoc-gen-grpc-java -Dversion=1.55.1 -Dclassifier=linux-loongarch_64 -Dpackaging=exe -Dfile=/path/to/file
[ERROR] 
[ERROR]   Alternatively, if you host your own repository you can deploy the file there: 
[ERROR]       mvn deploy:deploy-file -DgroupId=io.grpc -DartifactId=protoc-gen-grpc-java -Dversion=1.55.1 -Dclassifier=linux-loongarch_64 -Dpackaging=exe -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
[ERROR] 
[ERROR]   Path to dependency: 
[ERROR]         1) org.apache.seata:seata-grpc:jar:2.8.0-SNAPSHOT
[ERROR]         2) io.grpc:protoc-gen-grpc-java:exe:linux-loongarch_64:1.55.1
[ERROR] 
[ERROR] ----------
[ERROR] 1 required artifact is missing.
[ERROR] 
[ERROR] for artifact: 
[ERROR]   org.apache.seata:seata-grpc:jar:2.8.0-SNAPSHOT
[ERROR] 
[ERROR] from the specified remote repositories:
[ERROR]   loongarch (https://maven.loongnix.cn/loongarch/maven, releases=true, snapshots=false),
[ERROR]   aliyun (https://maven.aliyun.com/repository/public, releases=true, snapshots=false),
[ERROR]   apache.snapshots (https://repository.apache.org/snapshots, releases=false, snapshots=true),
[ERROR]   central (https://repo.maven.apache.org/maven2, releases=true, snapshots=false)
[ERROR] 
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <args> -rf :seata-grpc
root@88e40ffc5856:/workspace/incubator-seata#

解决方案

由于龙芯 https://maven.loongnix.cn/loongarch/maven 仓库的 io.grpc:protoc-gen-grpc-java 版本没有 1.55.1，需要选择已存在的版本，如：1.54.2

第三次编译打包

使用参数 -Dgrpc.version=1.54.2 修复上次问题

命令

mvn -V clean package -DskipTests -Dgrpc.version=1.54.2

问题

[INFO] Installing node version v19.5.0
[INFO] Downloading https://unofficial-builds.nodejs.org/download/release/v19.5.0/node-v19.5.0-linux-loong64.tar.gz to /root/.m2/repository/com/github/eirslett/node/19.5.0/node-19.5.0-linux-loong64.tar.gz
[INFO] No proxies configured
[INFO] No proxy was configured, downloading directly
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for Seata Parent POM 2.8.0-SNAPSHOT 2.8.0-SNAPSHOT:
[INFO] 
[INFO] Seata Build 2.8.0-SNAPSHOT ......................... SUCCESS [  1.307 s]
[INFO] Seata Parent POM 2.8.0-SNAPSHOT .................... SUCCESS [  2.280 s]
......
[INFO] json-common-jackson3 2.8.0-SNAPSHOT ................ SUCCESS [  2.339 s]
[INFO] seata-test 2.8.0-SNAPSHOT .......................... SUCCESS [ 17.855 s]
[INFO] seata-console 2.8.0-SNAPSHOT ....................... FAILURE [ 20.303 s]
[INFO] seata-namingserver 2.8.0-SNAPSHOT .................. SKIPPED
[INFO] seata-distribution 2.8.0-SNAPSHOT .................. SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  09:05 min
[INFO] Finished at: 2026-08-09T03:00:28Z
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.15.0:install-node-and-npm (install node and npm) on project seata-console: Could not download Node.js: Got error code 404 from the server. -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.15.0:install-node-and-npm (install node and npm) on project seata-console: Could not download Node.js: Got error code 404 from the server.
    at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 (MojoExecutor.java:333)
    at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute (MojoExecutor.java:316)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:212)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:174)
    at org.apache.maven.lifecycle.internal.MojoExecutor.access$000 (MojoExecutor.java:75)
    at org.apache.maven.lifecycle.internal.MojoExecutor$1.run (MojoExecutor.java:162)
    at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute (DefaultMojosExecutionStrategy.java:39)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:159)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:105)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:73)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:53)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:118)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:919)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:285)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:207)
    at jdk.internal.reflect.DirectMethodHandleAccessor.invoke (DirectMethodHandleAccessor.java:104)
    at java.lang.reflect.Method.invoke (Method.java:565)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:255)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:201)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:362)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:314)
Caused by: org.apache.maven.plugin.MojoFailureException: Could not download Node.js: Got error code 404 from the server.
    at com.github.eirslett.maven.plugins.frontend.mojo.MojoUtils.toMojoFailureException (MojoUtils.java:28)
    at com.github.eirslett.maven.plugins.frontend.mojo.AbstractFrontendMojo.execute (AbstractFrontendMojo.java:103)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:126)
    at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 (MojoExecutor.java:328)
    at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute (MojoExecutor.java:316)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:212)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:174)
    at org.apache.maven.lifecycle.internal.MojoExecutor.access$000 (MojoExecutor.java:75)
    at org.apache.maven.lifecycle.internal.MojoExecutor$1.run (MojoExecutor.java:162)
    at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute (DefaultMojosExecutionStrategy.java:39)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:159)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:105)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:73)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:53)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:118)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:919)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:285)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:207)
    at jdk.internal.reflect.DirectMethodHandleAccessor.invoke (DirectMethodHandleAccessor.java:104)
    at java.lang.reflect.Method.invoke (Method.java:565)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:255)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:201)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:362)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:314)
Caused by: com.github.eirslett.maven.plugins.frontend.lib.InstallationException: Could not download Node.js
    at com.github.eirslett.maven.plugins.frontend.lib.NodeInstaller.installNodeDefault (NodeInstaller.java:208)
    at com.github.eirslett.maven.plugins.frontend.lib.NodeInstaller.install (NodeInstaller.java:95)
    at com.github.eirslett.maven.plugins.frontend.mojo.InstallNodeAndNpmMojo.execute (InstallNodeAndNpmMojo.java:100)
    at com.github.eirslett.maven.plugins.frontend.mojo.AbstractFrontendMojo.execute (AbstractFrontendMojo.java:94)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:126)
    at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 (MojoExecutor.java:328)
    at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute (MojoExecutor.java:316)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:212)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:174)
    at org.apache.maven.lifecycle.internal.MojoExecutor.access$000 (MojoExecutor.java:75)
    at org.apache.maven.lifecycle.internal.MojoExecutor$1.run (MojoExecutor.java:162)
    at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute (DefaultMojosExecutionStrategy.java:39)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:159)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:105)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:73)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:53)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:118)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:919)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:285)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:207)
    at jdk.internal.reflect.DirectMethodHandleAccessor.invoke (DirectMethodHandleAccessor.java:104)
    at java.lang.reflect.Method.invoke (Method.java:565)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:255)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:201)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:362)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:314)
Caused by: com.github.eirslett.maven.plugins.frontend.lib.DownloadException: Got error code 404 from the server.
    at com.github.eirslett.maven.plugins.frontend.lib.DefaultFileDownloader.download (FileDownloader.java:70)
    at com.github.eirslett.maven.plugins.frontend.lib.NodeInstaller.downloadFile (NodeInstaller.java:338)
    at com.github.eirslett.maven.plugins.frontend.lib.NodeInstaller.downloadFileIfMissing (NodeInstaller.java:331)
    at com.github.eirslett.maven.plugins.frontend.lib.NodeInstaller.installNodeDefault (NodeInstaller.java:141)
    at com.github.eirslett.maven.plugins.frontend.lib.NodeInstaller.install (NodeInstaller.java:95)
    at com.github.eirslett.maven.plugins.frontend.mojo.InstallNodeAndNpmMojo.execute (InstallNodeAndNpmMojo.java:100)
    at com.github.eirslett.maven.plugins.frontend.mojo.AbstractFrontendMojo.execute (AbstractFrontendMojo.java:94)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:126)
    at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 (MojoExecutor.java:328)
    at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute (MojoExecutor.java:316)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:212)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:174)
    at org.apache.maven.lifecycle.internal.MojoExecutor.access$000 (MojoExecutor.java:75)
    at org.apache.maven.lifecycle.internal.MojoExecutor$1.run (MojoExecutor.java:162)
    at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute (DefaultMojosExecutionStrategy.java:39)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:159)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:105)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:73)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:53)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:118)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:919)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:285)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:207)
    at jdk.internal.reflect.DirectMethodHandleAccessor.invoke (DirectMethodHandleAccessor.java:104)
    at java.lang.reflect.Method.invoke (Method.java:565)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:255)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:201)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:362)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:314)
[ERROR] 
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <args> -rf :seata-console
root@3b92fe34a154:/workspace/incubator-seata#

解决方案

在 https://unofficial-builds.nodejs.org/download/release/ 中下载的支持龙芯架构的 node 没有 v19.5.0 版本，需要选择已存在的版本，如：v20.20.2

第四次编译打包：解决所有问题

使用参数 -DnodeVersion=v20.20.2 修复上次问题

由于在 https://unofficial-builds.nodejs.org/download/release/ 下载速度较慢，可以考虑使用 -DnodeDownloadRoot= 修改下载地址

只要保持自定义下载地址与 https://unofficial-builds.nodejs.org/download/release/ 下载地址规则相同即可

mvn -V clean package -DskipTests -Dgrpc.version=1.54.2 -DnodeVersion=v20.20.2

xuxiaowei · July 28, 2026, 8:55pm

确保仓库顺序

第一优先级：https://maven.loongnix.cn/loongarch/maven
第二优先级：https://maven.aliyun.com/repository/public

删除 frontend-maven-plugin 相关的依赖与 node 版本

删除后，调整正确的仓库顺序后，重新执行编译，即可下载龙芯架构的版本

find ~/.m2/repository/com/github/eirslett/

ls -lah console/src/main/resources/static/console-fe/node

rm -rf /root/.m2/repository/com/github/eirslett/
rm -rf ./console/src/main/resources/static/console-fe/node

root@88e40ffc5856:/workspace/incubator-seata# find ~/.m2/repository/com/github/eirslett/
/root/.m2/repository/com/github/eirslett/
/root/.m2/repository/com/github/eirslett/frontend-maven-plugin
/root/.m2/repository/com/github/eirslett/frontend-maven-plugin/1.15.0
/root/.m2/repository/com/github/eirslett/frontend-maven-plugin/1.15.0/_remote.repositories
/root/.m2/repository/com/github/eirslett/frontend-maven-plugin/1.15.0/frontend-maven-plugin-1.15.0.jar.sha1
/root/.m2/repository/com/github/eirslett/frontend-maven-plugin/1.15.0/frontend-maven-plugin-1.15.0.pom
/root/.m2/repository/com/github/eirslett/frontend-maven-plugin/1.15.0/frontend-maven-plugin-1.15.0.jar
/root/.m2/repository/com/github/eirslett/frontend-maven-plugin/1.15.0/frontend-maven-plugin-1.15.0.pom.sha1
/root/.m2/repository/com/github/eirslett/frontend-plugin-core
/root/.m2/repository/com/github/eirslett/frontend-plugin-core/1.15.0
/root/.m2/repository/com/github/eirslett/frontend-plugin-core/1.15.0/frontend-plugin-core-1.15.0.jar.sha1
/root/.m2/repository/com/github/eirslett/frontend-plugin-core/1.15.0/_remote.repositories
/root/.m2/repository/com/github/eirslett/frontend-plugin-core/1.15.0/frontend-plugin-core-1.15.0.pom
/root/.m2/repository/com/github/eirslett/frontend-plugin-core/1.15.0/frontend-plugin-core-1.15.0.pom.sha1
/root/.m2/repository/com/github/eirslett/frontend-plugin-core/1.15.0/frontend-plugin-core-1.15.0.jar
/root/.m2/repository/com/github/eirslett/frontend-plugins
/root/.m2/repository/com/github/eirslett/frontend-plugins/1.15.0
/root/.m2/repository/com/github/eirslett/frontend-plugins/1.15.0/_remote.repositories
/root/.m2/repository/com/github/eirslett/frontend-plugins/1.15.0/frontend-plugins-1.15.0.pom
/root/.m2/repository/com/github/eirslett/frontend-plugins/1.15.0/frontend-plugins-1.15.0.pom.sha1
/root/.m2/repository/com/github/eirslett/node
/root/.m2/repository/com/github/eirslett/node/20.20.2
/root/.m2/repository/com/github/eirslett/node/20.20.2/node-20.20.2-linux-loong64.tar.gz
root@88e40ffc5856:/workspace/incubator-seata#

root@88e40ffc5856:/workspace/incubator-seata# ls -lah console/src/main/resources/static/console-fe/node
total 95M
drwxr-xr-x 3 root root 4.0K Jul 28 20:35 .
drwxr-xr-x 9 root root 4.0K Jul 28 20:35 ..
-rwxr-xr-x 1 root root  95M Jul 28 20:35 node
drwxr-xr-x 4 root root 4.0K Jul 28 20:35 node_modules
-rwxr--r-- 1 root root 2.1K Jul 28 20:35 npm
-rwxr--r-- 1 root root  538 Jul 28 20:35 npm.cmd
-rwxr--r-- 1 root root 2.1K Jul 28 20:35 npx
-rwxr--r-- 1 root root  538 Jul 28 20:35 npx.cmd
root@88e40ffc5856:/workspace/incubator-seata#

在 LoongArch64 (loong64) 龙芯 3B6000 如何编译 seata 分布式事务？

复现环境

修复已知问题

第一次编译打包

命令

问题

解决方案

settings.xml

第二次编译打包

命令

问题

解决方案

相关议题

第三次编译打包

命令

问题

解决方案

相关议题

第四次编译打包：解决所有问题

确保仓库顺序

删除 frontend-maven-plugin 相关的依赖与 node 版本