apache / apache/shardingsphere

Remove the dependency on the buildArg for `-H:+TreatAllTypeReachableConditionsAsTypeReached`, which was added in GraalVM Native Build Tools `1.0.0` and later

Open
#38,943 3 comments 0 reactions 1 assignee Claimed by @linghengqian View on GitHub
in: proxy native type: dependencies type: enhancement
Dominant language
Java
Stars
20.8k
Forks
6.9k
Avg merge
11h 35m
Merged PRs (30d)
326

Description

## Feature Request

**For English only**, other languages will not be accepted.

Please pay attention on issues you submitted, because we maybe need more details.
If no response anymore and we cannot make decision by current information, we will **close it**.

Please answer these questions before submitting your issue. Thanks!

### Is your feature request related to a problem?

- See https://github.com/apache/shardingsphere/issues/29052 .

### Describe the feature you would like.

- Remove the dependency on the buildArg for `-H:+TreatAllTypeReachableConditionsAsTypeReached`, which was added in GraalVM Native Build Tools `1.0.0` and later.
- Currently, the entire ShardingSphere project is still using `org.graalvm.buildtools:native-maven-plugin:0.11.5`. Once we switch to using `org.graalvm.buildtools:native-maven-plugin:1.1.3`, all GraalVM Native Image builds will fail. Moreover, the error log is almost identical to that of https://github.com/graalvm/native-build-tools/issues/873 . However, the problem is resolved by adding `-H:+TreatAllTypeReachableConditionsAsTypeReached` to the `pom.xml` file, indicating that some dependencies are passing outdated GraalVM Reachability Metadata.
- The current issue aims to track which upstream dependencies are passing these outdated GraalVM Reachability Metadata and simplify configuration on the ShardingSphere side once the upstream is fixed.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.