You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MergeSourceSetFoldersWorkaround has an empty fixedIn parameter. But actually the status in the linked issue is set:
Status: Won't Fix (Intended Behavior)
We tried to add @DoNotCacheByDefault but got performance regression from some of our benchmarks so we revert the change in I031cf4a63f8c45538cc5247d29e2d30d03cfe21e
Does it make sense to then still ship this workaround?
If Gradle teams still thinks this is required I would expect a new issue with some data to hold against their result.
The text was updated successfully, but these errors were encountered:
The disabling of caching was just a temporary workaround. It makes sense to remove the workaround. We need to figure out in which version it would make sense to start disabling it.
MergeSourceSetFoldersWorkaround has an empty
fixedIn
parameter. But actually the status in the linked issue is set:Does it make sense to then still ship this workaround?
If Gradle teams still thinks this is required I would expect a new issue with some data to hold against their result.
The text was updated successfully, but these errors were encountered: