Sam

Is this the exact copy n paste from what you're using, because I can't see why this would be wrong.

Yeah but when I try it I get the full stack trace.

> * Consider making use of kotlin-power-assert which will become part of the standard compiler plugin set ([KT-63607](https://youtrack.jetbrains.com/issue/KT-63607/Migrate-kotlin-power-assert-into-Kotlin-repository)). Should we ask them to consider supporting other types of function names,...

> Seems like functionality like this is already there: https://github.com/bnorm/kotlin-power-assert > > > The Gradle plugin allows configuring the functions which should be transformed with a list of fully-qualified function...

> I don't currently have an idea of what might work, but things will surely become clearer with some experimentation. It probably makes sense to do this early up and...

> * Consider/Check possibility/ignore gradle limitations on `TEST_AND_CONTAINER` > If you remember the problem, we wanted to merge FreeSpec into StringSpec and some other similar things. The problem was that...

Yeah kotest is setup to fold io.kotest stacktraces and things like that, so using my domain for tests is an easy way to avoid that. That should only be used...

> For breaking changes I think it is right time to upgrade gradle version to support java 17 and 21! > > for 6.0 I think this kind of major...

You can disable classgraph scanning by setting the system property or env var: kotest.framework.classpath.scanning.autoscan.disable=true

There are conflicts on the merge.