Skip to content

add module info #45

Closed
Task
#50
Closed
add module info#45
Task
#50
Labels
defectA defect in the system (not a bug!).
Milestone
1.2.0-stable

Description

@stephengold
stephengold
opened on Aug 18, 2025

JSnapLoader v1.1.1 does not define a module, so Java considers it part of the Unnamed Module.

For this reason, when jSnapLoader invokes the System.load() method, Java 24 issues a runtime warning:

WARNING: A restricted method in java.lang.System has been called

This warning can be suppressed using --enable-native-access=ALL-UNNAMED. However, this workaround is risky from a security standpoint because it might give access to large swaths of code that don't need such access.

To mitigate this risk, it would better if jSnapLoader defined its own module, which should probably be named electrostatic4j.snaploader.

Activity

  1. pavly-gerges
    added
    defectA defect in the system (not a bug!).
    on Oct 7, 2026
  2. pavly-gerges
    modified the milestones: 1.1.1-stable Release, 1.2.0-stable on Oct 8, 2026

  3. pavly-gerges commented on Oct 9, 2026

    @pavly-gerges
    pavly-gerges
    on Oct 9, 2026
    Member

    Notice that; Java Modules are supported from Java 9+. Therefore, once updated, jSnapLoader will not work anymore on applications compiled with Java 8.

  4. pavly-gerges commented on Oct 9, 2026

    @pavly-gerges
    pavly-gerges
    on Oct 9, 2026
    Member

    These used to cause annoying problems for platforms that were primarily dependent on Java 8 (e.g., Android). I don't know the new Android updates. However, I believe all Java 11 features are supported now.

  5. pavly-gerges
    linked a pull request that will close this issueJava modules and New Sonatype Infrastructure #50on Oct 9, 2026

  6. stephengold commented on Oct 9, 2026

    @stephengold
    stephengold
    on Oct 9, 2026
    ContributorAuthor

    As of 2026, I believe Java 21 support is more vital than Java 8 support, but I don't have any data to support that belief.
    Have you ever tested jSnapLoader with Java 8?

  7. pavly-gerges commented on Oct 9, 2026

    @pavly-gerges
    pavly-gerges
    on Oct 9, 2026
    Member

    6. As of 2026, I believe Java 21 support is more vital than Java 8 support, but I don't have any data to support that belief.
    Have you ever tested jSnapLoader with Java 8?

    jSnapLoader was first bundled with Serial4j that was working on Java 8; then upgraded to 19 w/o changing the code; since that, the library has been separated. It should work flawlessly as it uses legacy language features.

    For this reason, when jSnapLoader invokes the System.load() method, Java 24 issues a runtime warning:

    WARNING: A restricted method in java.lang.System has been called

    Furthermore, I believe this warning was thrown because of Gradle libraries, and not particularly from jSnapLoader:

    WARNING: A restricted method in java.lang.System has been called
WARNING: java.lang.System::load has been called by net.rubygrapefruit.platform.internal.NativeLibraryLoader in an unnamed module (file:/home/runner/.gradle/wrapper/dists/gradle-9.8.1-bin/a2l6ltp3k1vth6lwipzm5p2jp/gradle-9.8.1/lib/native-platform-0.22-milestone-29.jar)
WARNING: Use --enable-native-access=ALL-UNNAMED to avoid a warning for callers in this module
WARNING: Restricted methods will be blocked in a future release unless native access is enabled

    It is thrown even though after introducing modules.

    May you please test a standalone JAR?

  8. pavly-gerges commented on Oct 9, 2026

    @pavly-gerges
    pavly-gerges
    on Oct 9, 2026
    Member

    See:
    gradle/gradle#33608

  9. stephengold commented on Oct 9, 2026

    @stephengold
    stephengold
    on Oct 9, 2026
    ContributorAuthor

    Have you tried:

    $ ./gradlew :wrapper --gradle-version=9.8.1 && ./gradlew :wrapper

    ?

  10. pavly-gerges commented on Oct 10, 2026

    @pavly-gerges
    pavly-gerges
    on Oct 10, 2026
    Member

    9. Have you tried:
    $ ./gradlew :wrapper --gradle-version=9.8.1 && ./gradlew :wrapper

    No, I haven't. I've updated the gradle wrapper from the gradle properties.

  11. pavly-gerges commented on Oct 10, 2026

    @pavly-gerges
    pavly-gerges
    on Oct 10, 2026
    Member

    It seems that the JAR file has not been replaced; https://github.com/Electrostat-Lab/jSnapLoader/blob/master/gradle/wrapper/gradle-wrapper.jar.

  12. pavly-gerges commented on Oct 10, 2026

    @pavly-gerges
    pavly-gerges
    on Oct 10, 2026
    Member

    I will try to update the JAR file instead.

  13. pavly-gerges
    added the
    Task
    issue type on Oct 10, 2026

  14. stephengold commented on Oct 10, 2026

    @stephengold
    stephengold
    on Oct 10, 2026
    ContributorAuthor

    ./gradlew :wrapper --gradle-version=9.8.1 && ./gradlew :wrapper is the correct way to update Gradle to version 9.8.1. It manages the necessary changes to 4 files:

    • gradlew
    • gradlew.bat
    • gradle/wrapper/gradle-wrapper.jar and
    • gradle/wrapper/gradle-wrapper.properties .

    Merely updating the properties file and the JAR file isn't always sufficient to complete an upgrade.

  15. pavly-gerges
    closed this as completedin #50on Oct 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    defectA defect in the system (not a bug!).

    Type

    Task

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions