Skip to content
GitLab

[Kotlin][Multiplatform] Fix Kotlin Multiplatform Test

Merged Administrator requested to merge github/fork/Airthings/fix-multiplatform-test into master

Created by: tkirshboim

PR Description

Fixes #10898 (closed)

  • Remove obsolete GRADLE_METADATA Gradle preview flag from Kotlin Multiplatform settings.gradle.kts.mustache template file.
  • Update Kotlin Version to 1.5.31.
  • Update coroutines, serialization and ktor versions to the versions recommended for usage with Kotlin 1.5.31 (see https://kotlinlang.org/docs/releases.html#release-details).
  • Add a clean task to the Kotlin Multiplatform template pom.xml file to allow to easily clean the samples folder from previous build outputs.
  • Update the Kotlin Multiplatform sample to reflect the changes to the template.

Testing

To validate that this PR fixes the issue, run the Kotlin Multiplatform test from the project's root folder and see that the test completes successfully.

./mvnw clean integration-test -f samples/client/petstore/kotlin-multiplatform/pom.xml

CCs

Kotlin technical committee: @jimschubert @dr4ke616 @karismann @Zomzog @andrewemery @4brunu @yutaka0m

People working on previous change #10468 : @shadowsheep1

PR checklist

  • Read the contribution guidelines.
  • Pull Request title clearly describes the work in the pull request and Pull Request description provides details about how to validate the work. Missing information here may result in delayed response from the community.
  • Run the following to build the project and update samples: 
    ./mvnw clean package 
./bin/generate-samples.sh
./bin/utils/export_docs_generators.sh
    Commit all changed files. This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master. These must match the expectations made by your contribution. You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example ./bin/generate-samples.sh bin/configs/java*. For Windows users, please run the script in Git BASH.
  • File the PR against the correct branch: master (5.3.0), 6.0.x
  • If your PR is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request.