This message was deleted.

basically did a hard reset on how I was doing the configuration/view portions of this making my question here moot. Obligatory thanks to @Jendrik Johannes for this video clarifying some behaviors for me:

There are two potential pitfalls I can think of: 1. The task is not correctly added as artifact to the consumable. One thing to check is to run

outgoingVariants

for the producer project and check what it shows. (But you most likely have this correct) 2. A sneaky problem often is that if the dependency resolution is triggered too early during the configuration phase. Then the task would have needed to run before tasks run (which can't work). But instead of giving you a helpful error, Gradle just skips the task. I could imagine that this is what is happening. Debugging this is also not simple unfortunately. If this is the issue, you maybe unintentionally resolve the configuration when you configure the consuming task. One thing to debug this could be to put a breakpoint into your "artifactView" configuration closure to see when that is triggered. If you could share your configuration code of the consuming task here, I can take a look.

I suspect it was case 2. I hit a few errors while trying different things where it would yell at me for trying to read task outputs before the task had ran. (if I tried to pipe the task output into a intermediate configurable file collection instead of directly to the task property it would throw the error)