we haven’t plugged it into Kobalt yet. Now it wor...

# kobalt

[apatrida]

we haven’t plugged it into Kobalt yet. Now it works by pulling dependencies into local system, performing any of the back-in-time shading, and then feeding those into gradle or maven as-if they are local dependencies. For maven publishing, we need to do the same but still ensure that maven/gradle can see the artifact group/id/version information correctly to publish a valid pom