Why does when applying only

kotlin

plugin,

api

configuration doesn't work as expected(consumers don't see it as transitive dependency), only after applying

java-library

modules does it work. Is it intended?

yes - the

java-library

plugin is the one that creates the

api

configuration, and the

kotlin

plugin does not

No. Otherwise declaring

api

dependency in pure

kotlin

module would fail configuration, and it doesn't.

I thought you were talking about in the

build.gradle.kts

not existing as an accessory accessor

for me in a pure kotlin subproject just

kotlin("jvm")

in plugins idea and gradle do not even recognize

api

https://youtrack.jetbrains.com/issue/KT-28355 – this is actually the issue, the fix will be available in 1.3.20

Indeed it works with

1.3.20-eap-100