Hi Not sure if multiplatform channel is the right place and

Question

Hi Not sure if multiplatform channel is the right place and even not sure if that is possible So I am generating Kotlin response request data classes used by Ktor I d like to keep them separate from common module Created another module and included `api project generatedapi ` it as a dependency to common module It compiles and builds successfully but when I publish the project as a library those generated classes are not included so clients which are using multiplatform library cannot access them Does anybody tried to achive something similar like this or maybe know a way how to expose dependency classes to clients Thanks

Big Chungus · Answer

Either publish that module as well or add it as implementation

rsetkus · Answer

< Big Chungus> when say add it as implementation you mean dump generated classes into common module

Big Chungus · Answer

No i mean replace api to implementation on that dependency snippet you ve sent

rsetkus · Answer

```Cannot access class xx yy DataClass Check your module classpath for missing or conflicting dependencies```

Big Chungus · Answer

Is that from the lib consumer

rsetkus · Answer

Getting this error on client side on attempt to use a class

rsetkus · Answer

Yeah

Big Chungus · Answer

In that case you need to make your lib fat ish jar that includes that module explicitly

Big Chungus · Answer

Here s an <https gitlab com lt petuska hazelcast explorer blob develop hazelcast explorer client build gradle kts L83|example>

Big Chungus · Answer

And <https gitlab com lt petuska hazelcast explorer blob develop hazelcast explorer build gradle kts L94|here>

Big Chungus · Answer

Second example is better suited to you First one is embedded kotlin js as webjar

rsetkus · Answer

Yeah maybe the second example is something I am looking for Will give a try Ačiū

rsetkus · Answer

Not sure why but `jar` task is not found in my main multiplatform module Instead used `jvmJar` and that worked fine That works for Android but I suppose I d get the same issue for iOS thinking face

Big Chungus · Answer

You will In this case why not just publish your internal module

rsetkus · Answer

But client consumer would need to include specify in dependencies both libraries wouldn t it

Big Chungus · Answer

Nope

Big Chungus · Answer

Gradle maven would download that internal dependency as transitive

rsetkus · Answer

This is the thing I published the other module too Also I can see that on client consumer app s dependency tree library is pulled as transitive dependency but still on client consumer side I am getting error ```Cannot access class XXX Check your module classpath for missing or conflicting dependencies```

Big Chungus · Answer

Is your class public

rsetkus · Answer

Yes correct It is public

Big Chungus · Answer

Then I m out of ideas Can t help you more without seeing the actual code

rsetkus · Answer

No worries I ll try to make SSCCE a Simple Self Contained Correct Compilable Example and publish it on github for instance

Big Chungus · Answer

Tbh I m only interested in your gradlefiles and class signature So if you could remove all your source code and publish that I could have a proper look

rsetkus · Answer

Made gist files first Let me know if you more context

rsetkus · Answer

Big Chungus · Answer

Can you make a proper git repo replicating your project structure Will have a look at that first thing tomorrow

rsetkus · Answer

Yeah sure No problem Will post a link here

Big Chungus · Answer

Hold on I see you now have everything as implementation Can you try changing all dependencies to api and see if that works

rsetkus · Answer

Yeah that worked tada Changed absolutely all `implementation` to `api` I used `api` before but only for the other internal module and that didn t work

Big Chungus · Answer

Great Api didn t work before because you weren t publishing the internal module

Big Chungus · Answer

Api dependencies transitive dependencies that gradle will download for the consumer Implementation dependencies provided dependencies that gradle expects to already be on the classpath

rsetkus · Answer

I see Yeah probably you re right then I used `api` before I didn t publish it at that time Thanks a lot I owe a beer slightly smiling face