Seems like I ll need to switch JDK versions within the CI pi kotlinlang #announcements

Channels

100daysofcode

100daysofkotlin

100daysofkotlin-2021

androidgithubprojects

cincinnati-user-group

competitive-programming

event21-community-content

java-to-kotlin-refactoring

jvm-ir-backend-feedback

kotlin-multiplatform-contest

kotlinultimatechallenge

myndocs-oauth2-server

naming

navigation-architecture-component

practical-functional-programming

proguard

prozis-android-backup

refactoring-to-kotlin

russian-kotlinasfirst

skia-wasm-interop-temp

stayhungrystayfoolish

swagger-gradle-codegen

tricity-kotlin-user-group

Title

hhandoko

05/18/2017, 2:37 AM

Seems like I’ll need to switch JDK versions within the CI pipeline (compile first with JDK

1.8

then test with JDK

1.7

ilya.gorbunov

05/18/2017, 2:40 AM

hhandoko: You can specify JVM to run maven surefire plugin with, use

forkMode

and

jvm

configuration properties, like here: https://github.com/JetBrains/kotlin/blob/1.1.2/libraries/stdlib/jre7/pom.xml#L97

hhandoko

05/18/2017, 2:43 AM

Oh, what does that do? I thought

forkMode

is JVM forking for parallel test execution.

Silly me, switching JDK won’t work… I had another look at

forkMode

, but it raises another question. Is this simply running the test using JDK

1.7

(as it is seen on the env variable)?

ilya.gorbunov

05/18/2017, 4:08 AM

forkMode

specifies that a new JVM process must be forked to run tests, and

jvm

specifies which JVM to use.

4 Views

#announcements Join Slack