Yes, and I am using the newest 1.3-rc stuff permitting to have everything controlled from one gradle spot (i.e. sub-projects
js
and
jvm
defined in the same, top-level gradle file), and mostly, it works like a charm. So it's not a big deal. But that said, I
would like
gradle publish
to work properly too ... Do you use the
maven-publish
plugin? Should I define somehow that it is OK not to publish the
common
source set? That's my theory, in fact, that gradle tries to publish stuff from
jsMain
, then from
jvmMain
and finally from
commonMain
... But I don't know where to interrupt this behaviour ...