Skip to content

Conversation

@simolus3
Copy link
Contributor

@simolus3 simolus3 commented Dec 3, 2025

This avoids the use of allprojects and subprojects for regular builds, which seems to be recommended ("you should use convention plugins or the proper APIs whenever possible"):

  • We had a top-level allprojects block setting up repositories that were already set up in settings.gradle.kts.
  • Some dependencies related to an intellij download were explicitly excluded. I assume this is a left-over from when we had our own SQLDelight plugin, I've removed the entire repository and nothing seemed to break.
  • Keeper, which we use to write on-device integration tests for Android, doesn't seem to work with the dependencyResolutionManagement block. Keeper is kind of unmaintained anyway, so this removes it by:
    • moving test logic from androidTest to main, and adding proguard rules ensuring the test utility does not get removed.
    • adding a few more proguard rules ensuring the test runner is also kept around.

Removing these brings us closer to enabling isolated projects in the future, which should speed up IDE sync.

Copy link
Contributor

@stevensJourney stevensJourney left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice!

@simolus3 simolus3 merged commit dd0e701 into main Dec 4, 2025
10 checks passed
@simolus3 simolus3 deleted the towards-isolated-projects branch December 4, 2025 08:14
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.

3 participants