I’m trying to integrate `kotlinc` compiler plugins...

# build-tools

[Tom Dyas]

I’m trying to integrate kotlinc compiler plugins into the Pants build tool’s experimental Kotlin backend. I am getting an AbstractMethodError in an integration test using the allopen plugin. Details in thread.

[Tom Dyas]

This is the exception message.

Untitled.cpp

[Tom Dyas]

The test command is ./pants test src/python/pants/backend/kotlin/compile/kotlinc_test.py -- -vv -k test_compile_with_kotlinc_plugin

[Tom Dyas]

The integration is not using a Kotlin distribution, but rather is resolving jars with Coursier. In this test, the allopen plugin came from resolving org.jetbrains.kotlin:kotlin-allopen:1.6.20

[Tom Dyas]

and then passing the resulting jars via -Xplugin

[Tom Dyas]

The compiler’s classpath was obtained by resolving org.jetbrains.kotlin:kotlin-compiler:1.6.20 and org.jetbrains.kotlin:kotlin-scripting-compler:1.6.20

[Tom Dyas]

The code is at https://github.com/pantsbuild/pants/pull/15184.

[Tom Dyas]

Is the approach of using Coursier-resolved jars a problem?

[tapchicoma]

tl;dr Kotlin relocates intellij dependencies for embeddable compiler artifact

[tapchicoma]

and parameter type for registerProjectComponent changes

[tapchicoma]

Check this line

[Tom Dyas]

hmm. So I just switched the Pants kotlin backend to use kotlin-compiler-embeddable for the compiler classpath and now the test passes. That jar shading is confusing!

[Tom Dyas]

and thanks for the advice!

[tapchicoma]

you could follow this issue, though not sure when or will it be resolved

[Tom Dyas]

Are there any downsides to using the -embeddable artifacts?

[tapchicoma]

right now - no

[Tom Dyas]

I’ll switch Pants to use the -embeddable artifacts then.