This message was deleted.
# community-supports
Slackbot
10/19/2023, 12:24 PMThis message was deleted.
s
Sebastian Schuberth
10/19/2023, 12:32 PMYou're not alone. I'm running into similar issues when requiring a specific version of GraalVM. On a related note, also see https://github.com/graalvm/native-build-tools/issues/357#issuecomment-1764476744
m
melix
10/19/2023, 12:51 PMWe had to revert almost all changes which use toolchains because of such limitations.
melix
10/19/2023, 12:52 PMboth in GraalVM native build tools and the Micronaut builds. To be fair not all issues are because of toolchains support. Sometimes it's just that the behavior is surprising to people. Like having workflows on CI which run on 21, tests pass and when people use 21 in prod it fails... because the CI builds were configured to use 17 toolchains...
r
René
10/19/2023, 1:02 PMugh
René
10/19/2023, 1:05 PMthanks for the feedback @Sebastian Schuberth @melix
It feels like I ran into a problem that we as gradle team used to rant about all the time when it comes to dependency resolution in maven. That a downloaded artifact (here a jdk) is not tight to where it has been resolved from. The url where it was resolved from should work as an input for a toolchain.
2 Views