Closed TheDadda closed 3 weeks ago
This issue needs a decision from the team responsible for that area. They have been informed. Response time may vary.
@TheDadda Does the same happen with Gradle 8.10?
@gradle/bt-configuration What's our stance on using custom types as task inputs with CC? Do we need to document those rules? Should we support such use cases?
Yes, the Self-contained Reproducer Project is using the latest gradle version 8.11-rc-1
This is the intended behavior, and there’s no plan to change it. This issue will be closed.
We expect the set of types used as part of Task configuration states to be limited. For this particular use case we recommend composition over inheritance, i.e. to create a custom class that contains a ConcurrentHashMap
.
What can be improved is the failure message, we'll work on that.
Current Behavior
I'm launching the configuration cache feature for our android project, but I encountered the following exception when codec deal with a custom ConcurrentHashMap:
Expected Behavior
I debug the gradle daemon process and found the codec encode and decode the custom ConcurrentHashMap as a normal ConcurrentHashmap, the custom ConcurrentHashMap class contains some fields, and i expected:
Context (optional)
No response
Self-contained Reproducer Project
./gradlew :app:customMapTask
, you will encounter the same exceptionGradle version
gradle-8.11-rc-1
Build scan URL (optional)
No response
Your Environment (optional)
No response