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

Publish platform for easier consumption #102

Open
trevjonez opened this issue Jul 29, 2020 · 2 comments
Open

Publish platform for easier consumption #102

trevjonez opened this issue Jul 29, 2020 · 2 comments

Comments

@trevjonez
Copy link

I think this project would be a good candidate for publishing a platform BOM to make consumption easier when pulling multiple packages.

https://docs.gradle.org/current/userguide/java_platform_plugin.html#sec:java_platform_publishing

@ychescale9
Copy link
Member

Thanks and yes this is in my backlog 😃 . One thing I'm not quite sure is if it still offers benefits if we're are already managing all the dependencies in a single place e.g. in buildSrc/dependencies.kt? How would the configurations look like in a typical multi-module Android project?

@trevjonez
Copy link
Author

precompiled script helpers is one popular way to do it, though not how I choose to. I try to rely on gradle provided functionality wherever possible rather than reinvent yet another way of handling things.

consumption in my mind would be roughly:

// Root build.gradle.kts
allProjects {
  dependencies {
    val flowBindingVersion: String by project // From root gradle.properties
    api(platform("io.github.reactivecircus.flowbinding:flowbinding-bom:$flowBindingVersion"))
  }
}

any place else using the libraries:

dependencies {
  api("io.github.reactivecircus.flowbinding:flowbinding-activity")
}

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

No branches or pull requests

2 participants