fwcd / fwcd/kotlin-debug-adapter
Improve resolution of compiled project classes
- Dominant language
- Kotlin
- Stars
- 150
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
Description
The Kotlin Debug Adapter currently relies on [hardcoded paths](https://github.com/fwcd/kotlin-debug-adapter/blob/a2a2332a081286256c790d7eb51cf0798d808fab/adapter/src/main/kotlin/org/javacs/ktda/classpath/ProjectClassesResolver.kt#L14), which is not a very robust solution. A possible solution would be to write (and invoke) a Gradle script, like we do to locate dependencies, but for [output classes](https://docs.gradle.org/current/dsl/org.gradle.api.tasks.SourceSetOutput.html).
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with adapter/src/main/kotlin/org/javacs/ktda/classpath/ProjectClassesResolver.kt, especially its hardcoded paths, and compare it with the existing Gradle-based dependency lookup. Trace how the Kotlin Debug Adapter invokes dependency resolution. Done means compiled project output classes are resolved through the project configuration rather than fixed paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100