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

Consider moving away from subprojects block for subproject configuration #1990

Open
sebersole opened this issue Sep 12, 2024 · 0 comments
Open
Labels
build Something related to the build

Comments

@sebersole
Copy link
Member

Using subprojects {} from build is considered an anti-pattern. Actually, referencing any project from another is consider an anit-pattern. It forces all of the projects to be evaluated and configured even if running tasks in just one.

In ORM, e.g., we instead use common script fragments applied to subprojects as appropriate.

An even better option is local plugins to accomplish this - I have just not done this yet with ORM which is more complex.

@DavideD DavideD added build Something related to the build problem A limitation or source of discomfort and removed problem A limitation or source of discomfort labels Dec 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build Something related to the build
Projects
None yet
Development

No branches or pull requests

2 participants