This message was deleted.
# community-support
s
This message was deleted.
v
Can you share a build
--scan
?
d
sure one sec
👌 1
it looks like it is something from spring
e
why spring? that's almost certainly a plugin/buildscript classpath issue
d
ktor graalvm integration works fine
v
A build scan will most probably immediately uncover the culprit. 😉
d
hmm
e
graalvm plugin in multiple different projects buildscript classpathes may be the problem, they're all different classes
try adding it to the root project (apply false) or buildSrc dependencies
d
yeah it looks like i cannot use composite build 😞
e
no that isn't related to composite build
d
interesting
applying plugin (false) in root project seems to fix the issue
e
you'd need to do that with the kotlin gradle plugin too, if it weren't already in your buildSrc
v
Hm, is
GraalVMReachabilityMetadataService$Inject
something Gradle adds with the runtime decorations? It is not there in the plugins jar
e
I believe that Gradle defines that class to override
getParameters()
isn't that how all the other similar injections via abstract fun work?
v
Maybe, never noticed which classes it generates probably. 😄
And never touched that code path
d
Thanks for the help!
e
ah,
org.gradle.internal.instantiation.generator.AsmBackedClassGenerator.decorateAndInject()
generates
$Decorated
,
org.gradle.internal.instantiation.generator.AsmBackedClassGenerator.injectOnly()
generates
$Inject
❤️ 1