feat(java): support graalvm copy

[zhaommmmomo]

What does this PR do?

support graalvm copy

Related issues

#1742
#1679

Does this PR introduce any user-facing change?

• Does this PR introduce any public API change?
• Does this PR introduce any binary protocol compatibility change?

Benchmark

[chaokunyang]

Could we add some unit tests in graalvm_tests module? Maybe we could construct some complex objects in fury-test-core, and reuse it for tests in fury-core and graalvm_tests

[zhaommmmomo]

Could we add some unit tests in graalvm_tests module? Maybe we could construct some complex objects in fury-test-core, and reuse it for tests in fury-core and graalvm_tests

No problem. I haven't seen the graalvm_tests module before, so I wrote a temporary module test locally

[zhaommmmomo]

Could we add some unit tests in graalvm_tests module? Maybe we could construct some complex objects in fury-test-core, and reuse it for tests in fury-core and graalvm_tests

I want to confirm that graalvm copy, which mainly means that the native-image executes correctly under different object copies?

Because I noticed that there are some errors when executing the mvn -DskipTests=true -Pnative package command under the graalvm_tests module. Some classes also need to add --initialize-at-build-time=xxx, some of which are code generated

[chaokunyang]

Could we add some unit tests in graalvm_tests module? Maybe we could construct some complex objects in fury-test-core, and reuse it for tests in fury-core and graalvm_tests

I want to confirm that graalvm copy, which mainly means that the native-image executes correctly under different object copies?

Because I noticed that there are some errors when executing the mvn -DskipTests=true -Pnative package command under the graalvm_tests module. Some classes also need to add --initialize-at-build-time=xxx, some of which are code generated

Could you share your unit test code here? This should not happen, we generated all code at graalvm build time. Do you init Fury and register all serializers in a static scope?

[zhaommmmomo]

Could we add some unit tests in graalvm_tests module? Maybe we could construct some complex objects in fury-test-core, and reuse it for tests in fury-core and graalvm_tests

I want to confirm that graalvm copy, which mainly means that the native-image executes correctly under different object copies?
Because I noticed that there are some errors when executing the mvn -DskipTests=true -Pnative package command under the graalvm_tests module. Some classes also need to add --initialize-at-build-time=xxx, some of which are code generated

Could you share your unit test code here? This should not happen, we generated all code at graalvm build time. Do you init Fury and register all serializers in a static scope?

I used Example class under the graalvm_tests module for testing

[chaokunyang]

@zhaommmmomo Could you push your test code? I will give it a try. And which graalvm JDK are you using?

[zhaommmmomo]

@zhaommmmomo你能推送你的测试代码吗？我会试试。你使用的是哪个 graalvm JDK？

GraalVM version:

Fury version: 0.8.0-SNAPSHOT

Test code: org.apache.fury.graalvm.Main#main

native-image.properties:

CMD: mvn -DskipTests=true -Pnative package

Error msg:

[mbasso]

Hello,
I have tried to use Fury with GraalVM Native Image and encountered the same error reported by @zhaommmmomo (tests in the main branch, no code changes):

Because I noticed that there are some errors when executing the mvn -DskipTests=true -Pnative package command under the graalvm_tests module. Some classes also need to add --initialize-at-build-time=xxx, some of which are code generated

I am using a custom GraalVM build based on OpenJDK 21