Why isn't JNI already a target?
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
Research direction
Start with the toolkit's component and language-binding generation described in the project summary, and use the linked JNI overview for terminology. Done requires a decided scope for JNI support and an agreed validation target; this issue does not identify files, tests, or entry points.
Written by the indexing model from the issue text.
Description
Why isn't JNI (https://en.wikipedia.org/wiki/Java_Native_Interface) already a target?
- Dominant language
- Go
- Stars
- 54
- Forks
- 26
- PR merge metrics
- No merged PRs in 30d
Contributor guide
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 Autodesk/AutomaticComponentToolkit
-
Autodesk/AutomaticComponentToolkit#226 · 5 comments · 3 reactions · 3 assignees ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
Autodesk/AutomaticComponentToolkit#213 · 1 comment · 2 reactions ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
Autodesk/AutomaticComponentToolkit#188 · 1 comment ·
-
Autodesk/AutomaticComponentToolkit#162 · 1 reaction · 2 assignees ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
All issues in Autodesk/AutomaticComponentToolkit
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
bug group: validation priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
codecheckers/chekhov#51 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100