Matt Groth

I just discovered a workaround: ```kotlin tasks.withType().configureEach { systemProperty("kotest.framework.classpath.scanning.config.disable","true") systemProperty("kotest.framework.classpath.scanning.autoscan.disable","true") } ``` This prevents the error.

My recommendation is that as an essential fix, Kotest should find a way to catch this exception and report a more informative error message to the user. Otherwise, the error...

https://kotest.io/docs/framework/project-config.html https://kotest.io/docs/next/framework/extensions/extensions-introduction.html

Hey @sksamuel, thank you for the update. Just to confirm, will both of these be disabled by default in 6.0? - `kotest.framework.classpath.scanning.config.disable` - `kotest.framework.classpath.scanning.autoscan.disable`

I just started having this issue. my specs: OSX: 10.12.4 ruby 2.4.1p111

Two main problems here: 1. The Language Addition feature should work more transparently. Users don't need this information 2. The check mark is information that users do need to quickly...

I know that this is probably something for JetBrains to fix in their plugin API, but in the meantime I do appreciate you keeping this open. Maybe we can bounce...