[help] how to fix error: class org.graalvm.buildtools.gradle.internal.GraalVMReachabilityMetadataService$Inject cannot be cast to class org.graalvm.buildtools.gradle.in ternal.GraalVMReachabilityMetadataService

[lost22git]

Issue description

version => 4.0.0-M1

native build error:

> class org.graalvm.buildtools.gradle.internal.GraalVMReachabilityMetadataService$Inject cannot be cast to class org.graalvm.buildtools.gradle.in
ternal.GraalVMReachabilityMetadataService (org.graalvm.buildtools.gradle.internal.GraalVMReachabilityMetadataService$Inject is in unnamed module 
of loader org.gradle.internal.classloader.VisitableURLClassLoader @7c519acc; org.graalvm.buildtools.gradle.internal.GraalVMReachabilityMetadataService is in unnamed module of loader org.gradle.internal.classloader.VisitableURLClassLoader @7ef5359d)

[melix]

Please provide more information about how to reproduce this problem. Which version of Gradle you are using, etc. 4.0.0-M1 is a pre-release of the Gradle Plugin aimed for Micronaut 4.

[melix]

I could reproduce and this turns out to be the same issue as gradle/gradle#17559

The workaround is to put the plugins on your build script classpath.

[msgilligan]

I ran into this issue in a Gradle multi-project build where there are two Micronaut apps and three command-line tools that are not using Micronaut that needed to include the 'org.graalvm.buildtools.native' plugin directly. The workaround for me (seems to be) using the following in the command-line tool subprojects:

id("io.micronaut.application") version "${micronautAppGradlePluginVersion}"

instead of:

id 'org.graalvm.buildtools.native' version '0.9.28'

I'd rather not have those subprojects pick up a Micronaut dependency, but the workaround seems to work.

[steventen]

We ended up using id("io.micronaut.minimal.application") to "solve" this issue, since we don't rely on GraalVM in our project