Open funky-eyes opened 2 days ago
Hi, could you share the specific build steps?
I tried running mvn compile -DskipTests=true
.
The version.json
for the 2.2.0 branch shows {"version":"2.2.0"}
, and for the 2.x branch, it shows {"version":"2.3.0-SNAPSHOT"}
.
That looks normal.
My build environment includes Node.js v20.17.0, npm 10.8.2, and Maven 3.9.9 on Windows 11 amd64.
Hi,您能提供一下具体的构建步骤吗?我尝试 mvn compile -DskipTests=true
命令构建。
2.2.0 分支的version.json 显示{"version":"2.2.0"}
;2.x 分支的version.json 显示{"version":"2.3.0-SNAPSHOT"}
。似乎是正常的?
我的编译环境:Node.js v20.17.0 & npm 10.8.2 & Maven 3.9.9 on Windows11 amd64.
Ⅰ. Issue Description
打包的时候明确了版本指向revision这个变量,而这个变量在打包日志里可以看到是生效的,但是对于version.js来说是无效的。 During packaging, the version is explicitly pointed to the revision variable, which can be seen as effective in the packaging logs. However, it is ineffective for version.js.
Ⅱ. Describe what happened
If there is an exception, please attach the exception trace:
Ⅲ. Describe what you expected to happen
Ⅳ. How to reproduce it (as minimally and precisely as possible)
Minimal yet complete reproducer code (or URL to code):
Ⅴ. Anything else we need to know?
Ⅵ. Environment:
java -version
):uname -a
):