Request: JNA-only and JNI-only published separately
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 58
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
I know nothing about the underlying implementation (so feel free to correct my misinterpretation) but a quick glance tells me that there's both a JNA-only and JNI-only implementation, and that the user may freely choose between the two, but only one should be used at runtime.
If so, I believe it would be better if there are separate packages published that users could depend on: one for JNA-only, one for JNI-only, and one for both. Right now, the jar artifact contains both, so for example, even though I'm using only the JNA implementation, I also have the JNI binaries unnecessarily included and thus unused.
I'm using Gradle to include this library as a dependency, and there may be a way to transform the jar artifact, but it seems complicated to do so. It would really be great if the JNA and JNI implementations are available as separate modules.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by examining the published jar artifact and the Gradle dependency setup described in the issue. Determine how the JNA-only, JNI-only, and combined modules should be represented, then verify that each published module contains only its intended implementation and that users can depend on it independently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100