Autodesk / Autodesk/AutomaticComponentToolkit
Why isn't JNI already a target?
Open
- Dominant language
- Go
- Stars
- 53
- Forks
- 26
- PR merge metrics
- No merged PRs in 30d
Description
Why isn't JNI (https://en.wikipedia.org/wiki/Java_Native_Interface) already a target?
Contributor guide
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.
Assessment
- Tech stack
- go, java
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100