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

Use convention plugins instead of shared subproject block #1263

Open
tweksteen opened this issue Nov 25, 2024 · 0 comments
Open

Use convention plugins instead of shared subproject block #1263

tweksteen opened this issue Nov 25, 2024 · 0 comments
Assignees

Comments

@tweksteen
Copy link
Member

The current setup to share the logic/dependencies between projects is to use a subproject {} block in the root project's build.gradle. This is not the best practice, as this creates an overlap of configurations that are specific to only some subprojects (for instance, the Android dependencies are only applied to Android subproject). Here are a couple of symptoms of the issue:

The official documentation recommends defining a convention plugin to share common traits between the build files.

From my reading of the root build.gradle. I think there are at least 2 conventions that we could define: built for Android or built for OpenJDK (see the current boolean androidProject).

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

1 participant