https://gradle.com/ logo
Join Slack
Powered by
This message was deleted.
# community-support
s
This message was deleted.
p
Hi Michal, The snippet above doesn't show where a reference to a 
Configuration
object is kept from the task. Doc can be found here https://docs.gradle.org/nightly/userguide/configuration_cache.html#config_cache:requirements:disallowed_types A 
Configuration
can be used for many things, you need to figure out how it is used and replace this with supported inputs. Could you share the place where the 
Configuration
is wired to the task? Or share the configuration cache html report, stacktraces in there should be enough to figure this out.
FTR there's a #C013WEPGQF9 channel for the next time you have a question about it 😉 Let's continue in this thread
m
Hi, thank you. Next time I'll use the channel
configuration-cache-report.html
p
The 
MRGenerator
reference from the task drags a lot of unsupported state.
via 
SourceSet
instances
SourceSet
instances aren't supported either by the configuration cache as stated in the doc
In this case I think you'd need a clearer separation between the state required to configure the tasks, and the task inputs. So that the former isn't referenced from the tasks.
Typically, 
GenerateMultiplatformResourcesTask.inputFiles
should be a 
ConfigurableFileCollection
instead. And the plugin should set it to ~ 
generator.generators.flatMap { it.inputFiles }
. That way the task doesn't need to hold references to all the configuration state.
Does the above make sense?
m
Thank you very much I think it makes sense, I'll try to incorporate it.
2 Views
Open in Slack
PreviousNext
Powered by