Cannot change usage of dependency configuration 'xxx' after it has been included in dependency resolution.

[sergeys-opera]

Cannot change usage of dependency configuration 'xxx' after it has been included in dependency resolution.

[jaredsburrows]

I have had this plugin applied to a project of mine - https://github.com/jaredsburrows/android-gif-search. It has now been migrated to ksp instead of kapt / annotationProcessor. I have not been able to reproduce this.

I can look into removing these warnings produced by the plugin scanning the configurations.

[t-beckmann]

Actually I think setting configuration.isCanBeResolved = true at https://github.com/jaredsburrows/gradle-license-plugin/blob/master/gradle-license-plugin/src/main/kotlin/com/jaredsburrows/license/LicenseReportTask.kt#L161 is not necessary.

[jaredsburrows]

Is this the same as #234? Also, why is configuration.isCanBeResolved = true not necessary?

[sergeys-opera]

Is this the same as #234?

Probably, yes.

My workaround for this issue is:

    // Silence excessive warning messages from "license[Debug|Release]Report" task,
    // see https://github.com/jaredsburrows/gradle-license-plugin/issues/338
    forEachTask(predicate = { it.name == "license${variantName}Report" }) {
        it.notCompatibleWithConfigurationCache("Not implemented")
        (it.logger as ContextAwareTaskLogger).setMessageRewriter { logLevel, message ->
            if (logLevel == LogLevel.WARN && message.startsWith(
                    "Cannot resolve configuration"
                )
            ) null else message
        }
    }

I couldn't get rid of the error messages by using mustRunAfter/dependsOn as suggested in #234. The project where I see the issue is an Android project if that matters.
I also call notCompatibleWithConfigurationCache on the license task as it's not yet (version 0.9.4) compatible with the configuration cache.

[t-beckmann]

For those interested, the meaning of those flags is discussed at https://docs.gradle.org/7.5.1/userguide/declaring_dependencies.html#sec:resolvable-consumable-configs.

Setting the isCanBeResolved turns producer and internal configurations to consumers. In the project I am working on doing so has unexpected side-effects on the Gradle build cache, so that it no longer matches!

Admittedly I do not fully understand the effect on the build cache, but I could resolve it by running the license plugin in a separate Gradle invocation separate from all other tasks. My guess is changing isCanBeResolved leads to a different order of dependencies in other configurations...

I am saying changing the flag should not be necessary because a configuration that is not resolvable contributes files to the build only if it is resolved indirectly via some other configuration extending upon it. But in that case the files in question are part of the extending configuration as well and so are picked up by the license plugin nevertheless.