Split the maven artifact into native libraries and core-jna
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- java
- Domain
- build-system
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.
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.
- Dominant language
- Java
- Stars
- 8.9k
- Forks
- 1.7k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from java-native-access/jna
-
`Native.typeOptions` never releases library interfaces, leaking classloadersPossibly taken @curforever claimed this 1 day ago. Open
Difficulty 4/5 1-2 days Newbie friendliness 48/100
java-native-access/jna#1742 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 66/100
java-native-access/jna#1738 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
java-native-access/jna#1736 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
java-native-access/jna#1717 ·
-
Windows32Exception - The parameter is incorrectPossibly taken @marktech0813 claimed this 337 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 35/100
java-native-access/jna#1700 · 11 comments ·
All issues in java-native-access/jna
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
NationalSecurityAgency/ghidra#9884 ·
Maintainers usually reply within 2 days
-
Status: Pending Review Type: Feature Request
Difficulty 1/5 Under an hour Newbie friendliness 82/100
OpenRefine/OpenRefine#8019 ·
Maintainers usually reply within 1 day
-
`timer` rule rejects dates the engine acceptsPossibly taken @MFA-G claimed this today. Openbug ready
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
camunda/bpmnlint-plugin-camunda-compat#281 · 3 comments ·
Maintainers usually reply within 1 day
-
status: waiting-for-triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100