Skip to content

Migrate build configuration to Gradle Version Catalogs#886

Open
iscle wants to merge 1 commit intoFoedusProgramme:betafrom
iscle:version-catalog-migration
Open

Migrate build configuration to Gradle Version Catalogs#886
iscle wants to merge 1 commit intoFoedusProgramme:betafrom
iscle:version-catalog-migration

Conversation

@iscle
Copy link
Copy Markdown

@iscle iscle commented Apr 14, 2026

This PR migrates the built do use Version Catalogs for easier library management.

No actual versions were changed, they have all been kept the same as before.

- Create `gradle/libs.versions.toml` containing all project versions, libraries, and plugins.
- Refactor `build.gradle.kts` files across the project (`app`, `baselineprofile`, `hificore`, etc.) to use `libs` type-safe accessors.
- Replace hardcoded dependency strings and version variables with catalog aliases.
- Update plugin declarations to use the `alias()` syntax.
@AkaneTan
Copy link
Copy Markdown
Member

Hi, there's a reason that we're not using version catalog on gramophone, that is it is only convenient in large projects containing multiple libraries which require unified dependency version. Gramophone is not the suitable case apparently

@iscle
Copy link
Copy Markdown
Author

iscle commented Apr 14, 2026

Thanks for the reply! I think that even for small projects it's a good QoL improvement. It removes clutter from the build.gradle.kts file and helps keeping everything organized in its own file.

But of course, this comes down to developer preference! Feel free to close the pr if it's not something you're interested in :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants