Closed jerry3323 closed 5 months ago
java version is
Active code page: 65001 native-image 17.0.9 2023-10-17
GraalVM Runtime Environment Oracle GraalVM 17.0.9+11.1 (build 17.0.9+11-LTS-jvmci-23.0-b21)
Substrate VM Oracle GraalVM 17.0.9+11.1 (build 17.0.9+11-LTS, serial gc, compressed references)
quarkus version is 3.6.3
/cc @Karm (mandrel), @galderz (mandrel), @zakkak (mandrel,native-image)
Looks like a duplicate of https://github.com/quarkusio/quarkus/pull/37651
@jerboaa not sure about this as I backported the fix ^ in 3.6.3 and the OP says they are using 3.6.3.
@gsmet The version seems to be some GraalVM EE thing:
native-image 17.0.9 2023-10-17
GraalVM Runtime Environment Oracle GraalVM 17.0.9+11.1 (build 17.0.9+11-LTS-jvmci-23.0-b21)
Substrate VM Oracle GraalVM 17.0.9+11.1 (build 17.0.9+11-LTS, serial gc, compressed references)
Which I thought was addressed in: https://github.com/quarkusio/quarkus/pull/37651/files#diff-051cb47b90d1d76cca2441db9dca7a399e3f755a1a668463119bef7871b5d057R145-R148
But it could very well be that this Active code page: 65001
output is confusing it. So NVM me.
But it could very well be that this
Active code page: 65001
output is confusing it. So NVM me.
It looks like that's exactly the root of the issue:
[ERROR] Caused by: java.lang.IllegalArgumentException: Cannot parse version from output:
[ERROR] Active code page: 65001
@jerry3323 it looks like a local configuration/script issue. Although I have no experience with this kind of issue myself I suggest having a look at https://stackoverflow.com/questions/48183570/how-to-fix-windows-batch-file-for-command-returing-active-code-page-65001 and giving the suggestions there a try.
Is this still an issue?
Closing for the lack of feedback
Describe the bug
Expected behavior
No response
Actual behavior
No response
How to Reproduce?
No response
Output of
uname -a
orver
No response
Output of
java -version
No response
Quarkus version or git rev
No response
Build tool (ie. output of
mvnw --version
orgradlew --version
)No response
Additional information
No response