We're trying to convert a small app to be multipla...
# multiplatform
a
We're trying to convert a small app to be multiplatform -- one issue we're encountering is that in IntelliJ, the JVM platform module has dependencies on build kotlin-stdlib and kotlin-stdlib-common, which causes things like
buildSequence
to be unusable. It seems this happens just in a simple multiplatform template project too -- does anyone else get this? (currently working around by manually removing kotlin-stdlib-common from the project structure, which is a pain)
i
What version of Kotlin idea plugin do you use?
a
1.2.40
specifically, 1.2.40-release-IJ2018.1-1
i
I've checked the similar setup, and did not see major usability problems with
buildSequence
. What errors do you get? Are they reported by gradle build or by IDEA only?
a
They are reported by IDEA only, the Gradle build seems ok (and Project->Rebuild project reports no errors)
Sorry, I mean
buildString
rather than
buildSequence
it seems to be seeing the one version with a typealiased StringBuilder as distinct from the other
i
Yeah, that's known problem, unfortunately: https://youtrack.jetbrains.com/issue/KT-20406
a
Regarding the resources not being found on the classpath when launching - I made an example project here to illustrate https://github.com/araqnid/kthings
thanks for the pointer to the YT ticket
i
Thank you for the test project. We'll take a look at that problem with resources.
l
Hello, @araqnid. Do you have
Delegate IDE build/run actions to gradle
enabled? The option may be found through Settings > Build, execution, Deployment > Build Tools > Gradle > Runner
a
@Liliia I didn’t - activating that setting made the example find the resource, thank you
l
Cool, thanks. Currently, Kotlin MPP projects aren’t supported by JPS, so for a proper builds execution this option should be activated for MPP projects, as well as
Run tests using
set into
Gradle Test Runner
. There is a request to improve the usability, see https://youtrack.jetbrains.com/issue/KT-23577
a
Unfortunately it does seem to be a global option rather than a per-project one, but hopefully the overall experience will improve as multiplatform support matures