vss-processor-plugin - Configuration Cache Problems

[wba2hi]

Right now when the vss-processor-plugin is applied to a Gradle Project which uses the Gradle Build Configuration Cache the following message appears during build:

* What went wrong:
Configuration cache problems found in this build.

2 problems were found storing the configuration cache.
- Task `:app:generateVssModels` of type `org.eclipse.velocitas.vssprocessor.plugin.GenerateVssModelsTask`: cannot serialize object of type 'org.gradle.api.internal.project.DefaultProject', a subtype of 'org.gradle.api.Project', as these are not supported with the configuration cache.
  See https://docs.gradle.org/8.6/userguide/configuration_cache.html#config_cache:requirements:disallowed_types
- Task `:samples:generateVssModels` of type `org.eclipse.velocitas.vssprocessor.plugin.GenerateVssModelsTask`: cannot serialize object of type 'org.gradle.api.internal.project.DefaultProject', a subtype of 'org.gradle.api.Project', as these are not supported with the configuration cache.
  See https://docs.gradle.org/8.6/userguide/configuration_cache.html#config_cache:requirements:disallowed_types

See the complete report at file:///Users/wba2hi/git/kuksa-android-sdk/build/reports/configuration-cache/e6ltsoksz20u3i3ik1ptf2v6c/4g0xekfaocvaq8jssjdwlyfm7/configuration-cache-report.html

The generateVssModels task is defined by us, to generate the VSS Models based on the VSS specification.

Right now the vss-processor-plugin does nothing to mitigate this issue, which leads to the consumers of the plugin to manually add the following lines of code:

afterEvaluate {
    tasks.getByName("generateVssModels").notCompatibleWithConfigurationCache("")
}

However, this does not make the message / warning disappear, it only prevents the build from failing.