I have an extremely nested set of multi-module repositories that I am managing.
e.g.
-
uber-generic-
product-genericproduct-specific
-
I want to ship a set of common dependencies and configurations from the uber-generic layer.
It looks like a build-convention plugin would allow me ship both dependencies and task configurations.
Whereas a catalog would allow me to ship only the dependencies?
Are there any best practices in terms of what can be included in a build-convention?