Hey :wave: For KMMBridge, the podspec source URL generated by the MavenPublishArtifactManager may no...

# touchlab-tools

[Jazmine Barroga]

Hey 👋 For KMMBridge, the podspec source URL generated by the MavenPublishArtifactManager may not be always the same as the actual maven repo url. This happens when you set a different artifactId for the framework or the project.group is different from what is in the maven artifact directory. Is this a bug or just a config issue?

[russhwolf]

Can you give an example? It's probably a bug but I'm not sure I follow what you're trying to do.

[Jazmine Barroga]

In the MavenPublishArtifactManager the artifactPath generated by kmmBridge may not be always the same to the directory of the maven repository

For example, when uploading the xcframework we altered the artifactId to library-ios. while the kmmbridgeArtifactId becomes library-kmmbridge

[russhwolf]

Can you show some of your gradle config so I understand where you're setting the name?

[Jazmine Barroga]

Sure, here it is inside the publications block

subprojects { project ->
    ....
    publishing {
        afterEvaluate {
            publications {    
                KMMBridgeFramework(MavenPublication) {
                    artifactId = "$project.name-ios"
                }
            }
        }
        ....
    }

    kmmbridge {
        mavenPublishArtifacts(project, null, null)
        manualVersions()
        cocoapods(project, <repo>, true, false)
    }
}

[russhwolf]

Ok I see. I don't think that's a use-case we ever considered. Is there a reason you need to change that artifactId? It probably wouldn't be too much work to support changing it, but we've largely thought of that URL as an implementation detail and not something that people would want fine-grained control over.

[Jazmine Barroga]

We are releasing public SDKS and we want to hide as much implementation details as we can and being flexible in the naming allows us to organize our libraries better and provide more clarity to our users

[Jazmine Barroga]

What do you think? @russhwolf 😅

[russhwolf]

Are you making public KMP sdks or Swift sdks? A Swift consumer will see the url if they look closely but shouldn't ever need to reference it themselves.

In any event, throw a ticket in GitHub and link back to this convo and we'll take a look and see what makes sense. But probably won't have any movement until after Kotlinconf at the earliest.

[Jazmine Barroga]

Okay sure. Thank you 🙏

[russhwolf]

Actually, even a Kotlin consumer won't interact directly with that id and url, because it'll be behind a maven coordinate which you can control the name of. What are you doing where this comes up for your consumer?

[Jazmine Barroga]

it is in the podspec source url