"8-:-Xms1g", // Range from 8
                "17:-Xmx4g", // Exact 17
                "invalid:pattern", // Invalid pattern
                "18-:-XX:+UseZGC", // Range from 18 (should be excluded)
                "11:-XX:+UseG1GC", // Exact 11 (should be excluded)
                "17-:-XX:+UnlockExperimentalVMOptions" // Range from 17
        };

        String[] result = JvmUtil.filterJvmOptions(args);

  osgiTestDeploy(libs.kotlin.stdlib.osgi)
}

tasks.withType<Test> {
  dependsOn(copyOsgiTestDeployment)
  val javaVersion = project.testJavaVersion
  onlyIf("Tests require JDK 17") {
    javaVersion >= 17
  }

          <item index="17" class="java.lang.String" itemvalue="org.springframework.lang.NonNull" />
        </list>
      </value>
    </option>
  </component>
  <component name="ProjectRootManager" version="2" languageLevel="JDK_17" default="true" project-jdk-name="17" project-jdk-type="JavaSDK" />

  }
}

tasks.shadowJar {
  mergeServiceFiles()
}

tasks.withType<Test> {
  val javaVersion = project.testJavaVersion
  onlyIf("native build requires Java 17") {
    javaVersion > 17
  }
}

apply(plugin = "org.graalvm.buildtools.native")

configure<GraalVMExtension> {
  binaries {
    named("main") {
      imageName = "okcurl"

      - name: setup java
        uses: actions/setup-java@v5
        with:
          distribution: temurin
          java-version: 17
      - id: determine-sys-prop-args
        uses: actions/github-script@v8
        with:
          script: |
            if (context.payload.pull_request && context.payload.pull_request.head.repo.fork) {

The unicode package and associated support throughout the system has been upgraded from Unicode 15 to Unicode 17.
See the [Unicode 16.0.0](https://www.unicode.org/versions/Unicode16.0.0/) and
[Unicode 17.0.0](https://www.unicode.org/versions/Unicode17.0.0/)

However, this would limit the ability of the Gradle ecosystem plugin authors to take advantage of new Java features and improvements.

One example is when one of the most popular plugins started requiring Java 17 because the underlying framework behind the plugin began requiring 17, and code from the framework was used in the plugin itself.
What would have happened if Gradle was limited to _only Java 11_ at the time?

## Decision

# By default, build TF in C++ 17 mode.
common:android --cxxopt=-std=c++17
common:android --host_cxxopt=-std=c++17
common:ios --cxxopt=-std=c++17
common:ios --host_cxxopt=-std=c++17
common:linux --cxxopt=-std=c++17
common:linux --host_cxxopt=-std=c++17
common:macos --cxxopt=-std=c++17
common:macos --host_cxxopt=-std=c++17
common:windows --cxxopt=/std:c++17
common:windows --host_cxxopt=/std:c++17

    withDeviceTest {
      instrumentationRunner = "androidx.test.runner.AndroidJUnitRunner"
      execution = "HOST"
    }

    // SDK 35 needs 17, for now avoid trying to run on
    // multiple robolectric versions, since device tests
    // do that
    if (testJavaVersion >= 17) {
      withHostTest {
        isIncludeAndroidResources = true
      }
    }
  }

  sourceSets {
    val commonJvmAndroid =

        val expectedInstallationPaths = linuxPaths.joinToString(",")
        val expectedRunnerParams =
            listOf(
                "-PperformanceBaselines=%performance.baselines%",
                "-PtestJavaVersion=17",
                "-PtestJavaVendor=openjdk",
                "-PautoDownloadAndroidStudio=true",
                "-PrunAndroidStudioInHeadlessMode=true",
                "-Dorg.gradle.java.installations.auto-download=false",