What the developer wrote
Authored by Craig Raw
remove warnings on gradle test task
What changed, and why it matters
This commit only changes the test runner settings in the project's build file. It swaps some Java module-opening arguments for a different one that removes warnings during automated testing. There is no change to the actual wallet application code that users interact with, and nothing here suggests a security vulnerability or fix.
No security action needed. Treat as routine build hygiene.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff modifies the test block in build.gradle, replacing --add-opens=java.base/java.io=com.google.gson and --add-reads=org.flywaydb.core=java.desktop with --enable-native-access=ALL-UNNAMED. This is a build/test configuration cleanup intended to silence Gradle/JUnit warnings. No application source code is changed, and no security-relevant behavior is introduced or patched.
Changed components
build.gradle test task configurationInspect captured patch +3 / −3
diff --git a/build.gradle b/build.gradle
index cf1a50b..e818d64 100644
--- a/build.gradle
+++ b/build.gradle
@@ -135,7 +135,7 @@ processResources {
test {
useJUnitPlatform()
- jvmArgs = ["--add-opens=java.base/java.io=ALL-UNNAMED", "--add-opens=java.base/java.io=com.google.gson", "--add-reads=org.flywaydb.core=java.desktop"]
+ jvmArgs = ["--add-opens=java.base/java.io=ALL-UNNAMED", "--enable-native-access=ALL-UNNAMED"]
}
application {
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.