What is the point of having the `danger-kotlin` cmdline tool to be Kotlin/Native target?
- Dominant language
- Kotlin
- Stars
- 542
- Forks
- 48
- PR merge metrics
- No merged PRs in 30d
Description
I'm not really sure what are the benefits of compiling `danger-kotlin` to several `Kotlin/Native` targets instead of shipping jar + simple wrapper script which launches the jar with JDK.
Since `danger-kotlin` already requires JDK to be available in the environment, wouldn't it be easier to support and ship the `.jar` + wrapper?
Contributor guide
No contributing guide indexed for this repository
Research direction
Review the danger-kotlin command-line tool distribution and its Kotlin/Native targets first. Compare the current targets with the proposed JAR plus wrapper-script approach, including the existing JDK requirement. Done means documenting and agreeing on whether the distribution model should change and which targets or packaging artifacts are affected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- build-system, cli
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100