Update build config, migrate away from deprecated Kotlin Multiplatform Gradle plugins

[aSemy]

When building the project locally I see an warning in the logs

The 'org.jetbrains.kotlin.platform.*' plugins are deprecated and will no longer be available in Kotlin 1.4.
Please migrate the project to the 'org.jetbrains.kotlin.multiplatform' plugin.
See: https://kotlinlang.org/docs/reference/building-mpp-with-gradle.html

problems running tests

I also experience problems when running the project locally, like not being able to run the tests of an individual subproject.

> ./gradlew :mock-common:test

And in IntelliJ if I try and run a test from a gutter icon I get an error

Execution failed for task ':mockk-common:test'.
> No tests found for given includes: [io.mockk.it.ValueClassTest](--tests filter)

I can also see that the build logic of the project is a bit scattered. There's some scripts in ./gradle/, and some project-local plugins in ./plugins/. Some of the Gradle scripts are in Groovy, but most are in Kotlin. It would be nicer if they were all Kotlin.

Proposal

Here's what I suggest:

• Combine MockK subprojects into Kotlin Multiplatform projects
  • mockk
  • mockk-dsl
  • mockk-agent
• Create buildSrc convention plugins for
  • Kotlin JVM/JS/Multiplatform
  • Publishing to Maven
  • common build scripts (./gradle/jacoco.gradle, ./gradle/upload.gradle etc)

This could be done incrementally, or in one big-bang. There wouldn't be any change to the source code - although it would be moved.

I am not an Android developer, so I don't know how the Android subprojects should be managed. Can they be combined with the Kotlin Multiplatform subprojects? Or maybe there should be a mockk-android subproject?

See also

These issues have a lot of interest. This ticket would provide a good basis for them.

• Feature: Support Kotlin/Native in MockK #58
• Feature: support Kotlin/JS in MockK #100
• Bug: Kotlin multiplatform project fails to build with mockk dependency #322

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. If you are sure that this issue is important and should not be marked as stale just ask to put an important label.

[aSemy]

This was completed in #855