With the release of Gradle 7.2-rc-1 it should now be possible to run our system tests on Java 17.

Comment From: wilkinsona

This still doesn't work. It now fails because the buildpack does not yet support Java 17:

> Running creator |  
-- | --
  | [creator]     ===> DETECTING |  
  | [creator]     5 of 18 buildpacks participating |  
  | [creator]     paketo-buildpacks/ca-certificates   2.3.2 |  
  | [creator]     paketo-buildpacks/bellsoft-liberica 8.2.0 |  
  | [creator]     paketo-buildpacks/executable-jar    5.1.2 |  
  | [creator]     paketo-buildpacks/dist-zip          4.1.2 |  
  | [creator]     paketo-buildpacks/spring-boot       4.4.2 |  
  | [creator]     ===> ANALYZING |  
  | [creator]     Previous image with name "docker.io/paketo-integration/gradle-9800951855375459452:latest" not found |  
  | [creator]     ===> RESTORING |  
  | [creator]     ===> BUILDING |  
  | [creator] |  
  | [creator]     Paketo CA Certificates Buildpack 2.3.2 |  
  | [creator]       https://github.com/paketo-buildpacks/ca-certificates |  
  | [creator]       Launch Helper: Contributing to layer |  
  | [creator]         Creating /layers/paketo-buildpacks_ca-certificates/helper/exec.d/ca-certificates-helper |  
  | [creator] |  
  | [creator]     Paketo BellSoft Liberica Buildpack 8.2.0 |  
  | [creator]       https://github.com/paketo-buildpacks/bellsoft-liberica |  
  | [creator]       Build Configuration: |  
  | [creator]         $BP_JVM_VERSION              17.*            the Java version |  
  | [creator]       Launch Configuration: |  
  | [creator]         $BPL_JVM_HEAD_ROOM           0               the headroom in memory calculation |  
  | [creator]         $BPL_JVM_LOADED_CLASS_COUNT  35% of classes  the number of loaded classes in memory calculation |  
  | [creator]         $BPL_JVM_THREAD_COUNT        250             the number of threads in memory calculation |  
  | [creator]         $JAVA_TOOL_OPTIONS                           the JVM launch flags |  
  | [creator]       No valid JRE available, providing matching JDK instead. Using a JDK at runtime has security implications. |  
  | [creator] |  
  | [creator]     Paketo BellSoft Liberica Buildpack 8.2.0 |  
  | [creator]       unable to find dependency |  
  | [creator]       no valid dependencies for jdk, 17.*, and io.buildpacks.stacks.bionic in [(jdk, 8.0.302, [io.buildpacks.stacks.bionic org.cloudfoundry.stacks.cflinuxfs3]) (jre, 8.0.302, [io.buildpacks.stacks.bionic org.cloudfoundry.stacks.cflinuxfs3]) (jdk, 11.0.12, [io.buildpacks.stacks.bionic org.cloudfoundry.stacks.cflinuxfs3]) (jre, 11.0.12, [io.buildpacks.stacks.bionic org.cloudfoundry.stacks.cflinuxfs3]) (jdk, 16.0.2, [io.buildpacks.stacks.bionic org.cloudfoundry.stacks.cflinuxfs3]) (jre, 16.0.2, [io.buildpacks.stacks.bionic org.cloudfoundry.stacks.cflinuxfs3]) (jvmkill, 1.16.0, [io.buildpacks.stacks.bionic org.cloudfoundry.stacks.cflinuxfs3])] |  
  | [creator]     ERROR: failed to build: exit status 1

Comment From: dreis2211

Wouldn't it make more sense to use the maximumCompatibleJavaVersion inside the build.gradle of those projects rather than removing the entire thing from CI? At least it would require less changes once it actually works.

Comment From: scottfrederick

Blocked by https://github.com/paketo-buildpacks/bellsoft-liberica/issues/127