This message was deleted.

Do something similar to what gradle itself does to manage tasks when fulfiling

implementation(project("subproject"))

dependencies

that would be by exposing configurations from

ParentImage

to be consumed in

ChildImage

For most things, Gradle shares outputs through variants: https://docs.gradle.org/current/userguide/cross_project_publications.html Here, this would mean exposing the both the version and the image as variants, and then consume those from the tasks, such that

calc-version

only depends on the

version

variant, which will trigger the

calc-version

task of the depended-on project. I'm not sure how well it fits with your needs though.

i'm pretty sure this is exactly what i need