Hello, I built a custom plugin which produces a zip artifact (schema resources) and potentially a jar artifact. Due to cosumer considerations - we need to care for Maven clients - the jar artifact is published under different coordinates than the main zip artifact. This is done by modifying the

artifactId

of the publication for the java artifact. This all works pretty well - except for the case where a project of this kind is being used in a multiproject build using a project reference. While Gradles dependency resolution can still work out the correct dependency via the artifact capabilities, publishing the dependent project fails with the infamous:

Publishing is not able to resolve a dependency on a project with multiple publications that have different coordinates.

project A: -> produces

group:a

(zip) -> produces

group:a-java

(jar) project B -> declares dependency

implementation(project(":a"))

Is there a workaround to coerce publishing of B to choose the correct coordinates (

group:a-java

)?