Hauke Radtki
04/04/2019, 8:00 AMSergio Casero
04/04/2019, 9:55 AMcommon
module targeting jvm
, ios
and js
2. common-client
targeting also android
Hauke Radtki
04/04/2019, 9:56 AMSergio Casero
04/04/2019, 9:57 AMPerson
and PersonView
Hauke Radtki
04/04/2019, 9:58 AMSergio Casero
04/04/2019, 10:00 AMHauke Radtki
04/04/2019, 10:02 AMSergio Casero
04/04/2019, 10:03 AMHauke Radtki
04/04/2019, 10:04 AMSergio Casero
04/04/2019, 11:27 AMh0tk3y
04/04/2019, 12:03 PMHauke Radtki
04/05/2019, 9:39 AM------ Java Application module
/
MPP module (JVM, Android, ios)
\
------ Android Library module
I'm using the org.jetbrains.kotlin.multiplatform
plugin. Thats why the MPP module contains a source set per target. And because I want to use Android features within the Android sourceSet of the MPP module, I have to apply the com.android.library
plugin for the whole MPP module. This is what causing the JVM module dependency to fail.
Also of course I need to have java code in the JVM and Android targets, as I'm having several expect/actual declarations that map to target specific types.
So under these circumstances: Is there a way to more cleanly express module dependencies than publishing to mavenLocal?