Compilation error when using kotest-assertions-core-jvm without kotest runner dependency
See original GitHub issueAccording to the docs, to use assertions library it should be enough to add one dependency io.kotest:kotest-assertions-core-jvm:<version>
. Unfortunately this doesn’t work, some matchers cannot be resolved and compilation fails. Here’s a minimal project that reproduces the problem: https://github.com/akowal/kotest-deps-issue/
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Quick Start - Kotest
For Gradle 4.6 and higher this is as simple as adding useJUnitPlatform() inside the tasks with type Test and then adding the Kotest...
Read more >Could not resolve io.kotest:kotest-runner-junit5-jvm:4.1.1 in ...
The problem with the configuration in question is that a JVM-only artifact ( io.kotest:kotest-runner-junit5-jvm ) appears as a dependency in ...
Read more >Maven Error: Failed to collect dependencies - When trying to ...
The error that I am getting be given below for reference. [ERROR] Failed to execute goal on project hello_world_mvn: Could not resolve dependencies...
Read more >Maven | Kotlin
Define the version of Kotlin you want to use via a kotlin.version ... The Kotlin Maven Plugin needs to be referenced to compile...
Read more >IntelliJ IDEA - Troubleshooting common Maven issues
This error usually indicates a problem with the compiler version compatibility, and you can check few places to fix it. For example, you...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I think its because in 4.0.x the dependency is implementation(project(“:kotest-assertions”)) In master its api. I’ll release 4.0.6 with this fix and some others.
When I use the latest snapshot, this problem doesn’t exist anymore. Here is a copy of @akowal’s repository that uses the latest snapshot: https://github.com/TheNumberOne/kotest-deps-issue