Open fwcd opened 3 years ago
The Kotlin Debug Adapter currently relies on hardcoded paths, 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.
The Kotlin Debug Adapter currently relies on hardcoded paths, 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.