java-native-access / java-native-access/jna
Split the maven artifact into native libraries and core-jna
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 8.9k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
Raised on the mailinglist:
I’d have liked to see separate Maven artifacts for “JNA with extract-at-runtime DLLs” and “JNA with pre-extracted DLLs, JNA not even trying to extract them” (even having the code path is scary, I did some serious debugging to make 150% sure that that can’t happen, but I’d have to redo that with every JNA update so I don’t like that one bit).
It should be investigated whether it is possible to split the native libraries from the core JNA code. This will not yield to a "JNA not even trying to extract them", but might be enough. The final nail in the coffin might be, that this might collide with the JPMS requirements.
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
The issue names no files, tests, or entry points. Start by reviewing the Maven artifact layout and the project's JPMS requirements; done means establishing whether native libraries can be separated from core JNA and documenting the resulting artifact constraints.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100