Hi,
unfortunately, the first pipeline run on JDK 16 failed due to the gradle-plugin not being built which the spring-boot-launch-script-tests and spring-boot-loader-tests depend upon. I've missed this on local tests, because previous runs populated my Gradle caches. I'm sorry for that.
As this is only a temporary solution until Gradle 7 is out, I chose to pragmatically disable things for now. There are other ways to fix this. E.g. by extending the toolchain DSL to enforce the compilation step, which would cause the spring-boot-gradle-plugin JAR to be built. Just let me know if you prefer that and I will play around with that idea.
Cheers, Christoph
Comment From: dreis2211
On a related note: Are you planning to eventually upgrade to Gradle 7 in 2.4.x at all?
Comment From: snicoll
On a related note: Are you planning to eventually upgrade to Gradle 7 in 2.4.x at all?
We're running against the 7.0 milestones on master only at this point.
Comment From: snicoll
Thanks for the follow-up Christoph. Let's see how it goes and we can refine if needed.
Comment From: dreis2211
And we have a green build ladies and gentlemen.