JPMS compatibility

[altavir]

Currently I can't use the serialization plugin in jlink due to split package problem. It could be fixed by package renaming.

[pdvrieze]

I haven't really tried looking at jdk versions after 8 (including java 9 modules). I'll have a look at trying to reorganize the packages to remove package name sharing.

[pdvrieze]

One of the issues is that there is not really a good path to (jigsaw) modular with multiplatform Kotlin. I may come up with a hack that will do so anyway, but it will be tricky (also due to output directories etc). I've added module name attributes in the manifest though (that's easy) and attempted to make all packages unique.

[altavir]

There are jpms-compatible stdlib artifacts. They go with modular qualifier. Also there is this thread.

As far, as I understand, you do not need to add a module manifest to make project work with jpms. You can use default module. The only thing you need to fix is to remove same package names in separate modules.

[pdvrieze]

The current head should not have any issues with modular package names anymore. I will wait until kotlin 1.3.40 to make a proper modular version as that version has withJava support that I can use to compile module-info.javafiles.

[pdvrieze]

This should be resolved with the 0.11.1.1 release. In addition there is the jigsaw branch that should be properly modular, but may create all kinds of issues due to having multiple jvm artifacts (one targeting jdk8, another targeting jdk9)

[pdvrieze]

@altavir I've added hopefully proper support in the moduleInfo branch. It would be good if you could check that it is correct.