baomidou / baomidou/dynamic-datasource
Fix nativeTest failures in CI under GraalVM Native Image
- Dominant language
- Java
- Stars
- 5.2k
- Forks
- 1.2k
- PR merge metrics
- No merged PRs in 30d
Description
**Is your feature request related to a problem? Please describe.**
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
- See https://github.com/baomidou/dynamic-datasource/actions/runs/20453121808/job/58769886305 .
**Describe the solution you'd like**
A clear and concise description of what you want to happen.
- The native test in CI under the GraalVM Native Image has failed. A further change to a Gradle-style approach is needed.
- The file https://github.com/baomidou/dynamic-datasource/blob/master/CONTRIBUTING.md also needs to be modified.
**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.
- Null.
**Additional context**
Add any other context or screenshots about the feature request here.
- Given that issues https://github.com/gradle/gradle/issues/17559 and https://github.com/graalvm/native-build-tools/issues/572 remain unresolved, bypassing this problem might seem odd. After all, Gradle's design is outdated compared to Maven. To be honest, I would be very grateful if someone were willing to fix the Gradle bug first.
Contributor guide
Research direction
Start with the failed nativeTest job in the linked GitHub Actions run and inspect the Gradle-style native-image setup. Update CONTRIBUTING.md as requested, then verify that the native test passes in CI and that the documented workflow reflects the change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, java
- Domain
- build-system, ci-cd, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100