linghengqian commented on issue #21051: URL: https://github.com/apache/shardingsphere/issues/21051#issuecomment-1251761246
- The answer is no, the build for ShardingSphere Proxy is almost certain to fail, which is influenced by many factors. - But once we have such a CI task to provide continuous tracking of build errors, we can submit Graal reachability metadata related to third-party libraries or ShardingSphere itself to https://github.com/oracle/graalvm-reachability-metadata , which will help the construction of ShardingSphere JDBC and ShardingSphere Proxy in GraalVM Native Image at the same time, and **finally** achieve the purpose of successful construction at a certain point **in the future**. - Considering that running Mockito in Native Image must rely on the integration of JUnit 5 Platform, it is impossible for such a test to work on the master branch of ShardingSphere, and the Graal metadata test corresponding to ShardingSphere needs to be placed at https://github.com/oracle/ graalvm-reachability-metadata to handle. -- 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]
