Skip to content

DOCS: Describe granting native library access - #563

Draft
oleksandrlazarenko-pi wants to merge 1 commit into
mainfrom
feature/476-native-access-docs
Draft

DOCS: Describe granting native library access#563
oleksandrlazarenko-pi wants to merge 1 commit into
mainfrom
feature/476-native-access-docs

Conversation

@oleksandrlazarenko-pi

Copy link
Copy Markdown
Contributor

Documentation half of #476.

On-premise device detection loads its native library through System.load, which
recent JDKs treat as a restricted method and will eventually block
(JEP 472). The load happens in LibLoader, which lives
in pipeline.engines.fiftyone, so the permission is granted against that package
rather than anything in this repository.

Adds a Native library access section to the README covering:

  • the classpath case (--enable-native-access=ALL-UNNAMED), which is the usual setup
    and stays unchanged;
  • the module path case
    (--enable-native-access=fiftyone.pipeline.engines.fiftyone), enabled by the module
    names added in 51Degrees/pipeline-java;
  • a pointer to the pipeline-java README for the full module name list and the caveats
    that apply on the module path.

No code changes. The device detection packages remain unnamed modules and need none -
unnamed modules can read named ones.

Depends on the companion pipeline-java PR, which adds the README section this one links
to; merge that first.

Documents --enable-native-access for classpath and module path setups, following the module names added in pipeline-java for #476.
@oleksandrlazarenko-pi oleksandrlazarenko-pi self-assigned this Jul 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant