Petition Gradle to support JVM-local configuration-cache

***Please thumbs-up this issue if you'd like Gradle to build this.*** TLDR: Unlike remote build cache, configuration cache is never going to be relocatable. Because of that, it might as well be a JVM-local cache (within-daemon), which removes the performance and incidental-complexity penalties of a serialization roundtrip. Spotless #986 hacks a workaround to demonstrate this approach, example API in [comment below](https://github.com/diffplug/spotless/issues/987#issuecomment-963664602). Gradle could support this natively so that configuration cache is faster to use and easier to develop plugins against. **EDIT: full no-asterisk support for configuration cache is available in Spotless 7.0.0+**

Posted by nedtwigg on Nov 8, 2021, 10:27 PM

Tags

• support (Software)

Related issues

• Add 65536 size support for maps
• TypeScript 7.1 Iteration Plan
• nvim-treeconfig: upstream nvim-treesitter
• Add the "action" and "method" attributes to <button>
• [FEATURE] Support multiple Connector accounts (same connector, different accounts) in Claude and Claude Code on the web (claude.ai/code)
• > We were imposed GitHub for so many exercises!