As I'm dogfooding the next release of <#CHJP9K00L|...
# multiplatforml
louiscad
02/04/2020, 4:19 PMAs I'm dogfooding the next release of #splitties, I noticed the source jars are empty for some modules.
It seems all modules that have common code have their sources properly put in the jar files, but all the modules that have only Android sources have no source files (only MANIFEST.MF).
Did anyone experience something similar when publishing a #multiplatform library? I'm wondering what can be the cause of this issue. Maybe I found a bug?
b
basher
02/04/2020, 4:27 PMhave you tried dokka 0.10.x? supposedly has better mpp support
k
Kris Wong
02/04/2020, 4:41 PMthat would affect javadoc jars rather than source jars 😛
b
basher
02/04/2020, 4:42 PMah whoops. read that wrong
k
Kris Wong
02/04/2020, 4:43 PMi have just been digging into publication, but I don't have any modules that don't include common source
l
louiscad
02/04/2020, 4:44 PMThat might be an incentive to kinda force me to get the project multiplatform harder 😅
louiscad
02/04/2020, 4:45 PMI think I'll try with empty Kotlin files in commonMain first as a workaround.
k
Kris Wong
02/04/2020, 4:48 PMyeah i've had to use a Dummy.kt in the past
Kris Wong
02/04/2020, 4:49 PMbut in the opposite way, as a target-specific source file
l
louiscad
02/04/2020, 5:00 PMI don't think having target-specific source files is needed anymore, right?
k
Kris Wong
02/04/2020, 5:01 PMin this specific case it is, because it's an umbrella project, and there is no other source - only exported dependencies
Kris Wong
02/04/2020, 5:01 PMso without that file it doesn't build the target
l
louiscad
02/04/2020, 7:30 PMInteresting, did you report that issue? For my m the issue I have, I think I'll, so I can reference it in the dummy files.
k
Kris Wong
02/04/2020, 7:30 PMi did not report it