Kotlin has the concept of "internal" code - code which is only accessible to the current "module". When running JMH benchmarks, I believe most developers would consider their benchmarks to be part of the same module. Right now, the JMH plugin does not resolve internal APIs from the main sourceset to the jmh sourceset.
Note that this change set only demonstrates the issue, it does not fix it.
Kotlin has the concept of "internal" code - code which is only accessible to the current "module". When running JMH benchmarks, I believe most developers would consider their benchmarks to be part of the same module. Right now, the JMH plugin does not resolve internal APIs from the main sourceset to the jmh sourceset.
Note that this change set only demonstrates the issue, it does not fix it.