Java 24 warning about native access

[parsaloi]

Describe the bug
Encountered a warning related to native invocation java.lang.System::load from an unnamed module

To Reproduce

// Gradle
dependencies {
    implementation("org.xerial:sqlite-jdbc:3.50.1.0")
}

<!--Maven-->
<dependencies>
    <dependency>
        <groupId>org.xerial</groupId>
        <artifactId>sqlite-jdbc</artifactId>
        <version>3.50.1.0</version>
    </dependency>
</dependencies>

Expected behavior
Add module-info.java to the related unnamed module.

Logs

WARNING: java.lang.System::load has been called by org.sqlite.SQLiteJDBCLoader in an unnamed module (file:///.gradle/caches/modules-2/files-2.1/org.xerial/sqlite-jdbc/3.50.1.0/6b1e999f284a82ae07f0e9ec455d3f2035614c6/sqlite-jdbc-3.50.1.0.jar)

Environment (please complete the following information):

• OS: Linux
• CPU architecture: amd64
• sqlite-jdbc version 3.50.1.0

Additional context
Using Gradle v8.14.2, Maven v3.9.9

[gotson]

We already provide it module-info.java

[parsaloi]

Maybe something else triggers the warning...🔍

[gotson]

Which java version are you using to run your app ? Was the warning not present with previous versions of sqlite-jdbc ?

I use sqlite-jdbc in my own app, running on Java 23, and i don't have such warning. It may be something you do in your build.

[parsaloi]

I was on previously Java 21 (no warning here) then recently upgraded to 24 where I encountered the warning which I linked to the "Integrity by Default" message from upstream

[gotson]

it seems to be related to Java 24, i found this: https://docs.oracle.com/en/java/javase/24/docs/api/java.base/java/lang/doc-files/RestrictedMethods.html

I don't know if it's possible to declare that the module uses native access, and i also don't know why the JVM reports that the call is from an unnamed module, while the module declaration is correct and contains the calling class.

[gotson]

I have done some more tests, and it seems that the fact that the call is from an unnamed module would be because your app itself is not using modules itself.

I have modified the Sample we have to use modules, and once i got that working, the warning is properly reported from the module we declare:

> java --module-path out:../target/sqlite-jdbc-3.50.1.1-SNAPSHOT.jar --module org.xerial.sample/org.xerial.sample.Sample
WARNING: A restricted method in java.lang.System has been called
WARNING: java.lang.System::load has been called by org.sqlite.SQLiteJDBCLoader in module org.xerial.sqlitejdbc (file:/Users/groebroeck/Dev/sqlite-jdbc/demo/../target/sqlite-jdbc-3.50.1.1-SNAPSHOT.jar)
WARNING: Use --enable-native-access=org.xerial.sqlitejdbc to avoid a warning for callers in this module
WARNING: Restricted methods will be blocked in a future release unless native access is enabled

Thus you will need to run your app with --enable-native-access=ALL-UNNAMED or to use modules in your app, and use -enable-native-access=org.xerial.sqlitejdbc

[gotson]

Depending on how you use the library, another way would be to add the Enable-Native-Access attribute in the JAR manifest (see https://docs.oracle.com/en/java/javase/24/docs/specs/jar/jar.html#jar-manifest).

[parsaloi]

Yeah, very useful advice @gotson
Your recommendations confirm that's the case as the call was from the app layer (not modular) that is using a custom sql dsl (modular) where a call from a simple test within the module boundary does not trigger the.warning

[gotson]

I'll close this and pin the issue so others can find the solution.