Add official local.properties support or other local way of configuration
It would be awesome if gradle officially supported `local.properties` so we don't' have to load the file into memory ourselves. Manually loading of `local.properties` is problematic because `providers.gradleProperty(..)` (required for configuration cache) does not work with this use case, so usage site code needs to be different, creating a maintenance burden --- ℹ️ 2026-06-09 by Gradle team: > We recognize the validity of the use cases highlighted by the discussion, but we are not ready to commit to the proposed solution as is. We will keep this issue open until we either support the use cases in some form or explicitly decide not to support some of them.
Posted by ZakTaccardi on Feb 19, 2020, 8:57 PM
Tags
Related issues
- some bike vendor told me that the biggest problem with regular to ebike conversion was that regular bike frames were not strong enough to...
- I think of this as the kiosk economy.
- What a goofy comment.
- There's lots of evidence for positive influences of Caffeine on the body (some negative as well), especially the brain.
- Compose support in WSLc
- [RFC] Roadmap to v2.0
Raise real-world problems, find people facing the same issue, and discuss solutions.3,500 issues0 comments
support (Other)
some bike vendor told me that the biggest problem with regular to ebike conversion was that regular bike frames were not strong enough to...
I think of this as the kiosk economy.
What a goofy comment.
There's lots of evidence for positive influences of Caffeine on the body (some negative as well), especially the brain.
Compose support in WSLc
[RFC] Roadmap to v2.0
[Feature]: Add TurboQuant Support for KV Cache Quantization
Support for AGENTS.md and .agents/skills/, the community has been asking since August 2025
Add official local.properties support or other local way of configuration
It would be awesome if gradle officially supported `local.properties` so we don't' have to load the file into memory ourselves. Manually loading of `local.properties` is problematic because `providers.gradleProperty(..)` (required for configuration cache) does not work with this use case, so usage site code needs to be different, creating a maintenance burden --- ℹ️ 2026-06-09 by Gradle team: > We recognize the validity of the use cases highlighted by the discussion, but we are not ready to commit to the proposed solution as is. We will keep this issue open until we either support the use cases in some form or explicitly decide not to support some of them.
Comments (0)
No comments yet. Start the discussion.