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
{{ message }}
Repository navigation
Graduate dependencyResolutionManagement.repositories to stable APIΒ #32443
changed the title [-]Graduate pluginManagement.repositories and dependencyResolutionManagement.repositories to stable API[/-][+]Graduate dependencyResolutionManagement.repositories to stable API[/+]on Feb 14, 2025
This has been the story of gradle right from the beginning: introducing half-baked solutions that remain unfinished for years and years, expecting users to just deal with it.
Activity
[-]Graduate pluginManagement.repositories and dependencyResolutionManagement.repositories to stable API[/-][+]Graduate dependencyResolutionManagement.repositories to stable API[/+]liutikas commentedon Feb 14, 2025
Related and probably blocked by #16616
jvandort commentedon Feb 18, 2025
This feature request is in the backlog of the relevant team and is prioritized by them.
It would be really great for an API to declare build-scoped repositories to be stable.
There are some things about the current API that hold us back from making it stable, in addition to the issues linked below:
Related issues:
settings.dependencyResolutionManagement.repositoriesModefrom Plugin<Project>sΒ #27260nskvortsov commentedon Dec 11, 2025
It is now even a "best practice": https://docs.gradle.org/current/userguide/best_practices_dependencies.html#set_up_repositories_in_settings
Please, promote the API
bartekpacia commentedon Jan 27, 2026
Introduced in Gradle 6.8, released January 2021.
5 years later it's still incubating
settings.gradle.kts: ignore warnings about incubating API usage
settings.gradle.kts: ignore warnings about incubating API usage
cleanup [build]: ignore warnings about incubating API usage
cleanup [build]: ignore warnings about incubating API usage
cleanup [build]: ignore warnings about incubating API usage
strindberg commentedon Feb 4, 2026
This has been the story of gradle right from the beginning: introducing half-baked solutions that remain unfinished for years and years, expecting users to just deal with it.