linghengqian commented on PR #30138: URL: https://github.com/apache/shardingsphere/pull/30138#issuecomment-1951630747
> Is this the problem you're having? [raphw/byte-buddy#1588](https://github.com/raphw/byte-buddy/issues/1588) - This is reasonable because using bytebuddy under GraalVM Native Image requires collecting additional JSON entries in the `buildArg` with `experimental-class-define-support=true` enabled. In raphw's github gist use case, I gave an example of using the Gradle Plugin implementation of GraalVM Native Build Tools to collect these files. Refer to the following link, - https://gist.github.com/raphw/e0f6864ddcad69630d839c2eebaad818?permalink_comment_id=4444676#gistcomment-4444676 - https://gist.github.com/raphw/e0f6864ddcad69630d839c2eebaad818 - https://github.com/graalvm/native-build-tools/blob/0.10.0/common/utils/src/main/java/org/graalvm/buildtools/agent/AgentConfiguration.java#L96 - In my opinion, those files are too large to be saved in multi-person collaboration git, so I did not discuss them in the current PR. I just opened an issue on the GraalVM side for a bug related to this experimental feature. Reference https://github.com/oracle/graal/issues/8396 . -  - The main reason the current PR is still in draft is that it contains some unrelated changes, which have been broken down into #30146 and #30145. - The current PR also contains some significant violations of the best practices defined by `testcontainers-java`, which require additional investigation. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
