This message was deleted.

Hmm… does an

ArtifactView

with a suitable component filter achieve this?

I just discovered component filter! checking now

it feels like it could… but I’ve never tried it

I think this works

it.componentFilter { componentIdentifier ->
  componentIdentifier is ModuleComponentIdentifier
}

👍

https://docs.gradle.org/current/userguide/dependency_locking.html#lock_all_configurations_in_one_build_execution ignoring the dependency locking bit, does that help?

interesting. We don't use dependency locking yet (though we should)

all you people using dependency locking before you started worrying about `failOnVersionConflict()`… 😛

I wanted to get us using platforms consistently first, because we have so many version conflicts across the build

I’m kidding… although my experience says this is a huge issue in open source projects… most cases are probably harmless… but people are stupidly slapdash about it.

I've started using this (well, a a bit complex in real usage but you get the gist) to define a platform based on the contents of a version catalog. seems to work pretty easily

that presupposes we're already using version catalogs << (but yes, it's a neat approach) 🔖

I happen to be doing exactly this today, trying to pre-populate the dependency cache on a docker image for ephemeral builds. Care to share your final solution? I’m about halfway there, got things resolving for specific configurations, now working on resolving all resolvable configurations…

jvm or android or both?

jvm

eh, here's the whole thing. You can simplify it dramatically by deleting the android-specific stuff https://gist.github.com/autonomousapps/f0133e58a612b6837f3f4f6554337035

Thanks for sharing! That helps immensely.