3 ms·
> your unfamiliarity with the JVM Correct! > a problem with multi-language, multi-compiler projects that none of the major build systems on the JVM really han
by rattray 10y ago
> your unfamiliarity with the JVM
Correct!
> a problem with multi-language, multi-compiler projects that none of the major build systems on the JVM really handle admirably
A bummer to hear – though I'm glad it's not just me. I tried using Kotlin with the Play Framework and did not have a great time. The hot-reloading features of Play didn't work with Kotlin at all, even with my attempts to `touch` a Java file whenever my Kotlin file changed (presumably they're recompiling more intelligently than I was).
Perhaps having SomeController.java and SomeController.kt in parallel, where the former imports the latter, and receives a `touch` or similar whenever the Kotlin file changes, might work? Or would you recon such a project to be a fool's errand?
- eropple 10y agoPlay isn't built for Kotlin and SBT is kind of a tire fire in general. I would suggest something more like Dropwizard for use with non-Scala JVM languages.
- EtienneK 10y agoOr Spring Boot, which is fantastic.
- eropple 10y agoI've never used Spring Boot - feel like plugging it a little? Dropwizard is the de facto in my neck of the woods, but I'm always looking for an improvement.
- rattray 10y agoThanks for the tip! Looks like there's even a starter example: https://github.com/doomspork/kotlin-dropwizard/ https://github.com/doomspork/kotlin-dropwizard/