New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is there a way to specify source code publish flag according to the targets? #743
Comments
please help me |
@yashctn88 What is your reason for only wanting to publish sources only for some targets? Having a sources jar is a requirement of maven central so there isn't much that can be done. The Kotlin Multiplatform plugin does have an API to disable the sources publication on a per target basis. You can try calling that after your @rvenky125 Please open a separate issue and include more information like your build configuration or a link to your project. |
@gabrielittner Thanks for the reply, my issues is not related to this issue(#743). I just asked him because for him all of components are uploading, for me it's not like that. my issue resolved by using below command to publish. the android and ios components are not uploading with the below command. |
@rvenky125 This is intended. Kotlin Multiplatform creates one publication for each target. If you're using the second command then you're just publishing the publication for the common source set. |
Is there a way to specify source code publish flag according to the targets? Like for example i am publishing kotlin multi platform library and i want for some specific target only to generated source jars not for all. Can this be configured ?
Here is my configuration, because
configure(
com.vanniktech.maven.publish.KotlinMultiplatform(
javadocJar = com.vanniktech.maven.publish.JavadocJar.Javadoc(),
sourcesJar = false,
androidVariantsToPublish = listOf("release")
)
)
The reason that i want to publish sources for specific target os that if i dont publish the source jar its getting rejected in the central.sonatype publish validation the sources are required
The text was updated successfully, but these errors were encountered: