Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Gradle fails for kotlin 1.6.10 and plugin version 1.5.0 #9

Open
bitkid opened this issue Feb 16, 2022 · 6 comments
Open

Gradle fails for kotlin 1.6.10 and plugin version 1.5.0 #9

bitkid opened this issue Feb 16, 2022 · 6 comments
Labels
bug Something isn't working

Comments

@bitkid
Copy link

bitkid commented Feb 16, 2022

thats what i get when i run ./gradlew test (gradle version 7.4)

java.lang.NoSuchMethodError: 'void org.jetbrains.kotlin.cli.common.messages.MessageCollector$DefaultImpls.report$default(org.jetbrains.kotlin.cli.common.messages.MessageCollector, org.jetbrains.kotlin.cli.common.messages.CompilerMessageSeverity, java.lang.String, org.jetbrains.kotlin.cli.common.messages.CompilerMessageLocation, int, java.lang.Object)'
at nl.fabianm.kotlin.plugin.generated.compiler.GeneratedComponentRegistrar.registerProjectComponents(GeneratedPlugin.kt:94)
at org.jetbrains.kotlin.cli.jvm.compiler.KotlinCoreEnvironment$Companion.registerExtensionsFromPlugins$cli(KotlinCoreEnvironment.kt:667)
at org.jetbrains.kotlin.cli.jvm.compiler.KotlinCoreEnvironment$ProjectEnvironment.registerExtensionsFromPlugins(KotlinCoreEnvironment.kt:169)
at org.jetbrains.kotlin.cli.jvm.compiler.KotlinCoreEnvironment.(KotlinCoreEnvironment.kt:216)
at org.jetbrains.kotlin.cli.jvm.compiler.KotlinCoreEnvironment.(KotlinCoreEnvironment.kt:111)
at org.jetbrains.kotlin.cli.jvm.compiler.KotlinCoreEnvironment$Companion.createForProduction(KotlinCoreEnvironment.kt:485)
at org.jetbrains.kotlin.cli.jvm.K2JVMCompiler.createCoreEnvironment(K2JVMCompiler.kt:227)
at org.jetbrains.kotlin.cli.jvm.K2JVMCompiler.doExecute(K2JVMCompiler.kt:153)
at org.jetbrains.kotlin.cli.jvm.K2JVMCompiler.doExecute(K2JVMCompiler.kt:52)
at org.jetbrains.kotlin.cli.common.CLICompiler.execImpl(CLICompiler.kt:92)
at org.jetbrains.kotlin.cli.common.CLICompiler.execImpl(CLICompiler.kt:44)
at org.jetbrains.kotlin.cli.common.CLITool.exec(CLITool.kt:98)
at org.jetbrains.kotlin.incremental.IncrementalJvmCompilerRunner.runCompiler(IncrementalJvmCompilerRunner.kt:434)
at org.jetbrains.kotlin.incremental.IncrementalJvmCompilerRunner.runCompiler(IncrementalJvmCompilerRunner.kt:120)
at org.jetbrains.kotlin.incremental.IncrementalCompilerRunner.compileIncrementally(IncrementalCompilerRunner.kt:357)
at org.jetbrains.kotlin.incremental.IncrementalCompilerRunner.compileIncrementally$default(IncrementalCompilerRunner.kt:299)
at org.jetbrains.kotlin.incremental.IncrementalCompilerRunner.compileImpl$rebuild(IncrementalCompilerRunner.kt:118)
at org.jetbrains.kotlin.incremental.IncrementalCompilerRunner.compileImpl(IncrementalCompilerRunner.kt:169)
at org.jetbrains.kotlin.incremental.IncrementalCompilerRunner.compile(IncrementalCompilerRunner.kt:80)
at org.jetbrains.kotlin.daemon.CompileServiceImplBase.execIncrementalCompiler(CompileServiceImpl.kt:622)
at org.jetbrains.kotlin.daemon.CompileServiceImplBase.access$execIncrementalCompiler(CompileServiceImpl.kt:100)
at org.jetbrains.kotlin.daemon.CompileServiceImpl.compile(CompileServiceImpl.kt:1713)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:564)
at java.rmi/sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:359)
at java.rmi/sun.rmi.transport.Transport$1.run(Transport.java:200)
at java.rmi/sun.rmi.transport.Transport$1.run(Transport.java:197)
at java.base/java.security.AccessController.doPrivileged(AccessController.java:691)
at java.rmi/sun.rmi.transport.Transport.serviceCall(Transport.java:196)
at java.rmi/sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:587)
at java.rmi/sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:828)
at java.rmi/sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:705)
at java.base/java.security.AccessController.doPrivileged(AccessController.java:391)
at java.rmi/sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:704)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:630)
at java.base/java.lang.Thread.run(Thread.java:832)

@fabianishere fabianishere added the bug Something isn't working label Feb 16, 2022
@fabianishere
Copy link
Owner

Currently, the plugin is not compatible with Kotlin 1.4+.

@bitkid
Copy link
Author

bitkid commented Feb 16, 2022

ah ok! thx

@fabianishere fabianishere changed the title gradle fails for kotlin 1.6.10 and plugin version 1.5.0 Gradle fails for kotlin 1.6.10 and plugin version 1.5.0 Feb 28, 2022
@shaunek
Copy link

shaunek commented Mar 25, 2022

Are there any plans to make this plugin compatible with Kotlin 1.4+? Our team has just decided internally to measure/track our code coverage better and this is definitely a hold up for us. :( Thanks.

@fabianishere
Copy link
Owner

Most of the functionality of this plugin is now supported natively by JaCoCo. Is there a reason you need this plugin to work?

I was not planning to work on compatibility with newer Kotlin versions, but if your team really needs this plugin, we might be able to arrange something.

@shaunek
Copy link

shaunek commented Mar 27, 2022

It is very possible I don't understand something basic here, but it is my understanding that JaCoCo will ignore methods with the lombok.Generated annotation, but as far as I have seen Kotlin-generated code doesn't have that annotation. My JaCoCo reports look like test coverage is horrible for a few reasons, but largely because the autogenerated getters/setters aren't explicitly called in tests. I'm hoping I can find a way that will allow me to write a data class in Kotlin with a couple of properties in the constructor, and avoid having to write a test that calls all the getters and setters to get to 100% code coverage on the report. I have been using Kotlin 1.6 with JaCoCo 0.8.7 if that matters.

Maybe you have a tip for me that will help me understand what I need to do in my Kotlin code (or maybe in the JaCoCo config) to get the Kotlin auto-generated getters/setters to be ignored?

@fabianishere
Copy link
Owner

Hmm, I was under the impression that JaCoCo supported Kotlin features natively by now. I think it is best to report these issues to the JaCoCo project so they can fix it directly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants