Has anyone seen an error like the following? The ...
# community-support
j
Has anyone seen an error like the following? The build succeeds, but the build scan fails with this error. If it matters, I'm using the jvm-dependency-conflict-resolution plugin in this project.
A build scan cannot be produced as an error occurred gathering build data.
Please report this problem via https://gradle.com/help and include the following via copy/paste: ---------- Gradle version: 7.6.4 Plugin version: 3.18.2 com.gradle.scan.plugin.internal.operations.a: Build operation dispatch of finished notification failed. Operation context: org.gradle.launcher.exec.RunAsBuildOperationBuildActionExecutor$1 (16880): {} org.gradle.execution.RunRootBuildWorkBuildOperationType$Details (33124): {getBuildStartTime=1747359390369} org.gradle.api.internal.tasks.execution.ExecuteTaskBuildOperationDetails (33142): {buildPath=:, taskPath=vault modelgraphViewMain, taskClass=com.autonomousapps.tasks.GraphViewTask, taskId=5276} org.gradle.api.internal.tasks.execution.TaskExecution$1 (33143): {} org.gradle.internal.execution.steps.CaptureStateBeforeExecutionStep$Operation$Details$1 (33144): {} org.gradle.api.internal.artifacts.configurations.ResolveConfigurationResolutionBuildOperationDetails (33146): {describe error: java.lang.IllegalAccessException: class com.gradle.scan.plugin.internal.operations.a cannot access a member of class org.gradle.api.internal.artifacts.configurations.ResolveConfigurationResolutionBuildOperationDetails with modifiers "public"} org.gradle.api.internal.artifacts.configurations.ResolveConfigurationResolutionBuildOperationDetails (33147): {describe error: java.lang.IllegalAccessException: class com.gradle.scan.plugin.internal.operations.a cannot access a member of class org.gradle.api.internal.artifacts.configurations.ResolveConfigurationResolutionBuildOperationDetails with modifiers "public"} Caused by: org.gradle.api.InvalidUserCodeException: Variant 'runtime' doesn't belong to resolved component 'org.springframeworkspring jcl6.1.19'. There's no resolved variant with the same name. Most likely you are using a variant from another component to get the dependencies of this component. at org.gradle.api.internal.artifacts.result.DefaultResolvedComponentResult.reportInvalidVariant(DefaultResolvedComponentResult.java:152) at org.gradle.api.internal.artifacts.result.DefaultResolvedComponentResult.getDependenciesForVariant(DefaultResolvedComponentResult.java:140) at com.gradle.scan.plugin.internal.c.i.a.j.a(SourceFile:36) at com.gradle.scan.plugin.internal.c.i.a.e$a.a(SourceFile:126) at com.gradle.scan.plugin.internal.c.i.a.e$a.a(SourceFile:150) at com.gradle.scan.plugin.internal.f.b.a(SourceFile:26) at com.gradle.scan.plugin.internal.c.i.a.e$a.a(SourceFile:126) at com.gradle.scan.plugin.internal.c.i.a.e$a.a(SourceFile:150) at com.gradle.scan.plugin.internal.f.b.a(SourceFile:26) at com.gradle.scan.plugin.internal.c.i.a.e$a.a(SourceFile:126) at com.gradle.scan.plugin.internal.c.i.a.e$a.a(SourceFile:150) at com.gradle.scan.plugin.internal.f.b.a(SourceFile:26) at com.gradle.scan.plugin.internal.c.i.a.e$a.a(SourceFile:126) at com.gradle.scan.plugin.internal.c.i.a.e$a.a(SourceFile:150) at com.gradle.scan.plugin.internal.f.b.a(SourceFile:26) at com.gradle.scan.plugin.internal.c.i.a.e$a.a(SourceFile:126) at com.gradle.scan.plugin.internal.c.i.a.e$a.a(SourceFile:150) at com.gradle.scan.plugin.internal.f.b.a(SourceFile:26) at com.gradle.scan.plugin.internal.c.i.a.e$a.a(SourceFile:126) at com.gradle.scan.plugin.internal.c.i.a.e$a.a(SourceFile:150) at com.gradle.scan.plugin.internal.f.b.a(SourceFile:26) at com.gradle.scan.plugin.internal.c.i.a.e$a.a(SourceFile:126) at com.gradle.scan.plugin.internal.c.i.a.e$a.a(SourceFile:150) at com.gradle.scan.plugin.internal.f.b.a(SourceFile:26) at com.gradle.scan.plugin.internal.c.i.a.e$a.a(SourceFile:126) at com.gradle.scan.plugin.internal.c.i.a.e$a.a(SourceFile:150) at com.gradle.scan.plugin.internal.f.b.a(SourceFile:26) at com.gradle.scan.plugin.internal.c.i.a.e$a.a(SourceFile:126) at com.gradle.scan.plugin.internal.c.i.a.e$a.a(SourceFile:150) at com.gradle.scan.plugin.internal.f.b.a(SourceFile:26) at com.gradle.scan.plugin.internal.c.i.a.e$a.a(SourceFile:126) at com.gradle.scan.plugin.internal.c.i.a.e$a.a(SourceFile:150) at com.gradle.scan.plugin.internal.f.b.a(SourceFile:26) at com.gradle.scan.plugin.internal.c.i.a.e$a.a(SourceFile:126) at com.gradle.scan.plugin.internal.c.i.a.e$a.a(SourceFile:105) at com.gradle.scan.plugin.internal.c.i.a.e$a.<init>(SourceFile:105) at com.gradle.scan.plugin.internal.c.i.a.e$a.b(SourceFile:116) at com.gradle.scan.plugin.internal.c.i.a.e$a.a(SourceFile:72) at com.gradle.scan.plugin.internal.c.i.a.e.a(SourceFile:51) at com.gradle.scan.plugin.internal.c.i.a.d.a(SourceFile:232) at com.gradle.scan.plugin.internal.c.i.c.lambda$attach$2(SourceFile:138) at com.gradle.scan.plugin.internal.operations.b$c.finished(SourceFile:154) at com.gradle.scan.plugin.internal.operations.b.a(SourceFile:65) at com.gradle.scan.plugin.internal.operations.n.a(SourceFile:56) at com.gradle.scan.plugin.internal.operations.d.a(SourceFile:136) at com.gradle.scan.plugin.internal.operations.h.a(SourceFile:51) at com.gradle.scan.plugin.internal.p.a$a.a(SourceFile:31) at com.gradle.scan.plugin.internal.p.a$a.a(SourceFile:20) at com.gradle.scan.plugin.internal.p.a.c(SourceFile:67)
While digging into this, I found when I added a direct dependency that was previously being pulled in transitively (ie spring-core), then the error appears. When I comment out this dependency, the scan succeeds. Both spring-core and spring-dcl are the same version. I'm still puzzled why Gradle attempts to get dependencies from the non-existent 'runtime' variant of spring-dcl when it should be getting dependencies from the 'runtimeElements' variant.
Also, spring-dcl is NOT a direct dependency of this build. However, the jvm-dependency-conflict-resolution plugin is configured to select spring-dcl as the capability for org.gradlex:commons-logging-impl.
l
Hey, Could you open an issue against the plugin? There might be something amiss in the way it works. It could also be a core Gradle issue but we could figure that out as a second step. Of course, if you manage to isolate this in a reproducer, that would be even better.