`publish` and `publishAndroid` are helpers that I ...

# gradle

[Davide Giuseppe Farella]

publish and publishAndroid are helpers that I wrote and internally do:

apply(plugin = "com.jfrog.bintray")
apply(plugin = "maven-publish")

group = ...
version = ...

afterEvaluate {
  publishing { ... }
  configure<BintrayExtension> { ... }
}

[Javier]

With maven publish plugin do you doesn't need bintray plugin

[Davide Giuseppe Farella]

Thanks, but I think that doesn’t make much differenec

[Javier]

I don't know, the setup is simpler and maybe fix the problem you have if it is caused by the bintray plugin

[Davide Giuseppe Farella]

Oh, so you’re talking about the configure block, I though only about the apply(plugin
Have you got any example of doc about that? I always found different parts of examples in different places

[Javier]

https://github.com/msink/kotlin-libui/blob/master/libui/build.gradle.kts

[Davide Giuseppe Farella]

Oh, look awesome 🤩 Thank you so much.
But I notice you’re not publishing on Android, which requires to be in the afterEvaluate block, that would make some more complication

[Davide Giuseppe Farella]

Hey @Javier could I bother you 10 mins? Just wanna check if my config is fine + a question about Android vs plain java vs multiplatfom publications

[Javier]

I am working, I can reply here when I can read you

[Javier]

BTW here you can see my settings for a jvm+Android library

[Javier]

https://github.com/JavierSegoviaCordoba/Core/blob/develop/buildSrc/src/main/kotlin/plugins/MavenPublish.gradle.kts

[Javier]

https://github.com/JavierSegoviaCordoba/Core/blob/develop/core/build.gradle.kts

[Davide Giuseppe Farella]

Thank you, I’m looking into it and I’ll get back to you only if I have further questions

[Davide Giuseppe Farella]

2 questions:
• cannot find out where you set the sources, in my script ( only Java / Android ) I had

val bundle = c.publicationsBundleBuilder(this@publishBlock)
val sourcesJar = tasks.create<Jar>("sourcesJar") {
    archiveClassifier.set("sources")
    from(bundle.sources)
}
afterEvaluate {
  artifact(javaDocsJar)
  artifact(tasks[if (isAndroid) "bundleReleaseAar" else "jar"])
  artifact(sourcesJar)
}

Where the pubBundleBuilder would return sourceSets["main"].allSource from java and android.sourceSets["main"].java.srcDirs on Android ( so ofc I needed 2 different methods to call for that and was not MultiPlatform ready I guess )
• How should I implement that commented part?

private fun Project.publish(lazy: Boolean, c: PublishConfig) {
    apply(plugin = "maven-publish")
    // apply(plugin = "signing")

    // signing {
    //     useGpgCmd()
    //     sign(publishing.publications)
    // }

[Javier]

I don't add the sources bundle manually because they are detected automatically, so I don't know why it is not working. Why do you need to add them manually?

For Android the only things I do is to add a snippet to the kotlin block as you can see here https://github.com/JavierSegoviaCordoba/Core/blob/develop/core/build.gradle.kts

android {
   publishLibraryVariants("release", "debug")
}

[Davide Giuseppe Farella]

IDK whether it’s needed, I just see it being done in all the project, but differently 😅
Is there any way I can include it in a kotlin-dsl module without the Android plugin?

[Javier]

Do you say a multiplatform library without Android?

[Javier]

https://github.com/JavierSegoviaCordoba/NetworkResponse

[Davide Giuseppe Farella]

No, I have a library with this publishing stuff, but I need 2 modules now: one with android and one without
publish / publishAndroid and in the one without Android I’m not applying the plugin ( and neither the dependency from the Android plugin, so I don’t have access to LibraryExtension for example )

[Davide Giuseppe Farella]

Sorry, I mean a library I include in the buildSrc of other project, to be more clear

[Davide Giuseppe Farella]

Would love to unify in a single module everything I can

[Javier]

Ah, the setup is different if it is multiplatform vs only Android. The Android dev web has the setup for it.

[Javier]

You can unify it but you will have to contact to bintray because they doesn't support add new target artifacts for released library

[Javier]

Because of this I moved to sonatype indeed

[Davide Giuseppe Farella]

So, sorry to iterate over that: what would be different to publish for Android only? I think I have kinda clear for multiplatform now

[Javier]

For multiplatform maven-publish is automatic (including android), for solo android no. https://developer.android.com/studio/build/maven-publish-plugin

[Javier]

I think is even easier to change the solo android library to multiplatform even only having code in commonMain and androidMain and publish so

[Davide Giuseppe Farella]

But that’s not up to me, it’s for public use 🙂

[Davide Giuseppe Farella]

Good, I just finished, but my publish task completes in 2 seconds without doin anything 😆😆

[Davide Giuseppe Farella]

Skipping task ‘:publish’ as it has no actions.