Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extract internal Gradle Service Injection framework into separate subprojects #28979

Open
alllex opened this issue Apr 26, 2024 · 0 comments
Open
Labels
a:chore Minor issue without significant impact in:core-utilities base services platform:core_runtime

Comments

@alllex
Copy link
Member

alllex commented Apr 26, 2024

Classes like ServiceRegistry and related machinery currently live in the bloated :base-services project. Since they provide an independent aspect of the Gradle architecture they should be located in their own subproject.

Let's split out a separate API subprojects as well, so subprojects that only want to declare services provided and consumed might do so without depending on the implementation.

The types from :java-language-extensions related to scopes should be moved to the new service registry API module, too.

@alllex alllex added a:chore Minor issue without significant impact platform:core_runtime labels Apr 26, 2024
@lptr lptr changed the title Extract internal Gradle Service Injection framework into a separate subproject Extract internal Gradle Service Injection framework into separate subprojects Apr 26, 2024
@mlopatkin mlopatkin added in:core-utilities base services and removed to-triage labels Apr 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a:chore Minor issue without significant impact in:core-utilities base services platform:core_runtime
Projects
None yet
Development

No branches or pull requests

2 participants