linghengqian opened a new pull request, #29000:
URL: https://github.com/apache/shardingsphere/pull/29000

   Fixes #21347.
   
   Changes proposed in this pull request:
     - This PR is introducing a series of path issues to solve 
https://github.com/apache/shardingsphere/issues/21347 .
     - This PR introduces the submodule 
`org.apache.shardingsphere:shardingsphere-infra-reachability-metadata` for 
hosting the GraalVM Reachability Metadata of ShardingSphere itself and some 
third-party libraries. This involves me personally not having much time in the 
central repository of GraalVM Reachability Metadata to handle PRs requested by 
the GraalVM Committer.
     - `org.apache.shardingsphere:shardingsphere-infra-reachability-metadata` 
will become an internal dependency of 
`org.apache.shardingsphere:shardingsphere-jdbc-core` to be passed out.
     - In order to check the usability under GraalVM Native Image, we need a 
subset of unit tests that avoids using third-party libraries such as Mockito 
that do not support use under Native Image to execute nativetest of GraalVM 
Native Build Tools. This subset of unit tests will be located at 
`org.apache.shardingsphere:shardingsphere-infra-nativetest`.
     - The unit test subset of 
`org.apache.shardingsphere:shardingsphere-infra-nativetest` is adapted from the 
ShardingSphere Example. Use YAML instead of Java API to define ShardingSphere's 
DataSource because this is closest to the actual application scenario - this is 
the actual meaning of native Test. We only focus on core functions in this unit 
test.
     - We introduce two Maven Profiles for this purpose, namely 
`generateMetadata` and `nativeTestInShardingSphere`. They both only manage 
`pluginManagement`. Submodules that need to use the relevant Profile will 
automatically introduce the relevant `plugin`. This involves best practices 
defined by GraalVM Native Build Tools. Refer to 
https://github.com/graalvm/native-build-tools/issues/490 .
     - The handling expected by this PR on the file system involves GraalVM's 
handling of the file system. Reference 
https://github.com/oracle/graal/issues/7682 .
   
   ---
   
   Before committing this PR, I'm sure that I have checked the following 
options:
   - [x] My code follows the [code of 
conduct](https://shardingsphere.apache.org/community/en/involved/conduct/code/) 
of this project.
   - [x] I have self-reviewed the commit code.
   - [x] I have (or in comment I request) added corresponding labels for the 
pull request.
   - [x] I have passed maven check locally : `./mvnw clean install -B -T1C 
-Dmaven.javadoc.skip -Dmaven.jacoco.skip -e`.
   - [x] I have made corresponding changes to the documentation.
   - [x] I have added corresponding unit tests for my changes.
   


-- 
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]

Reply via email to