With project isolation, is it ok to access root project lifecycle tasks from a sub project? e.g.

rootProject.tasks.named("check").configure { dependsOn(myTask) }

I'd vote "no".

It's not, but you can either define it as the other way in your root project, via hardcoded tasks or aggregation, or use a settings plugin. BTW there are no real lifecycle tasks, it is only a convention, but you can add actions to a „lifecycle“ task.

I'm not sure I follow. How would I do it from the root project or a settings plugin if I need to access the task from the subproject?

so usually you would define a 'check' task in every project. if for some reason it needs to be a single task it gets a bit tricky

Oh interesting. So I'd make a

check

task in each subproject, and hardcode that in the root using

subprojects

?

3 solutions 😄

you make a check task in every project. than you can call ./gradlew check and that executes all the checks

Good point 😅

Yeah, but this will configure all projects, if configure on demand is not a requirement.

well if your root project depends on all project it will also configure all projects 😄

Yeah sure, if you depend on all projects. But depending on all projects is not always the case, but it depends on your setup.

oh you right i read that wrong..

There's like 95% chance there's a check task in each subproject though. Java, Android and Kotlin plugins all add it (from base lifecycle plugin or so)

yup

It really depends on the setup, you need to test what's better, regarding performance vs effort (to maintain an explicit list).