From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

Does project A also correctly publishes Gradle module metadata for both modules?
And does project B resolves module metadata? (iirc, should be visible in debug logs)
If you only publish POMs, or if project B only resolves POMs, then you lose the variants information.

Can you maybe knit an <https://stackoverflow.com/help/mcve|MCVE> that shows your problem?
Might be easier to understand and properly advise then.

I'll try to get an MCVE going. <@UDC9Q9RD0> I am publishing metadata, yes (artifactory does have a uicomponents-1.2.0-SNAPSHOT.module). I'll check for the debug logs.

```2023-09-15T17:05:57.955+0200 [DEBUG] [org.gradle.api.internal.artifacts.repositories.resolver.ExternalResourceResolver] Metadata file found for module 'com.company.foundation:uicomponents:1.2.0-SNAPSHOT' in repository 'MavenLocal'.```
Yep, metadata is definitely found. Working off of mavenLocal() for now, but artifactory and ~/.m2 contain the same files, and the resolution problem happens no matter the source.

The squareTheme configuration gets visited first, and the roundTheme configuration gets to reuse the module metadata, but surely it wouldn't be using the wrong one, right?
```Found cached version of changing module 'com.company.foundation:uicomponents:1.2.0-SNAPSHOT' in 'MavenLocal'

Using cached module metadata for module 'com.company.foundation:uicomponents:1.2.0-SNAPSHOT' in 'MavenLocal'```

In this case, I’ve reversed it.
Project B only has `implementation(project())`  and from there either publish all or publish a variant. It works for us as our use case for this as we require the latitude both variants in the dimension to be different version numbers.
Project A would then define this as we would publish one for square and one for round. `squareThemeImplementation(libs.square.theme)` and `roundThemeImplementation(libs.round.theme)`