Hi. I’m trying to includeBuild kotlinx-rpc from a ...

# kotlinx-rpc

[arve]

Hi. I’m trying to includeBuild kotlinx-rpc from a different project but getting errors This also happens if i make a fresh gradle project and try to includeBuild only kotlinx-rpc. Has anyone had any luck doing this and have some pointers?

Building the project alone works fine

[Alexander Sysoev]

Hey! May I ask you about the problems you have?

[arve]

Hi. As background I’m evaluating how i can integrate kotlinx-rpc as the underlying communication solution for our internal service infrastructure.
I have a strict requirement of being able to pass ancillary (context) data on a per-call basis (such as trace ID, authentication, spans, etc.

While waiting for the ongoing discussion on github regarding plugins(/extensibility pipeline/extension points/pipelines) to land, or rather in an effort to push this discussion forward, I wanted to evaluate what changes are needed to support doing this via message headers in kRPC vs. making my own protocol for kotlinx-rpc. I suspect very minor adjustments are required so I want to see if I can save a ton of work in the interrim.

However, when I try to includeBuild(/path/to/kotlinx-rpc) in my project (as mentioned in contributing.md), i get the following error:

Settings file '/path/to/kotlinx-rpc/settings.gradle.kts' line: 26

Error resolving plugin [id: 'org.gradle.toolchains.foojay-resolver-convention', version: '0.9.0']
> A problem occurred configuring project ':kotlinx-rpc:gradle-plugin'.
> =========== Gradle Doctor Prescriptions ===========
  | For faster builds, use the parallel GC.          |
  | Add -XX:+UseParallelGC to the org.gradle.jvmargs |
  ====================================================

This also happens if I make an empty gradle project which only contains includeBuild(/path/to/kotlinx-rpc) and nothing else.


In summary I’m struggling to get “my own bulid” of krpc up and running in order to test with some modifications

[arve]

I tried maven local publish as well, but hit a wall with only “-jvm” suffix libraries being published.. Perhaps this is an easier route to fix but that would result in having to maually re-publish to mavenlocal after every adjustment

[arve]

I managed to solve this by publishing krpc to MavenLocal after each code change ✅