Support publications with grade metadata feature enabled

[minamoto79]

Gradle introduced gradle metadata feature in version 4.6 for which mostly used in native publications. It generate .module file for artifact which contains information about possible variants of artifact and configuration attributes for resolving. This file skipped by current version of plugin.

PR #230 realise metadata file publishing.

[h0tk3y]

+1 for this feature, as Kotlin Multiplatform projects now support publishing Gradle module metadata for simplifying dependency management. Is this going to be supported in the Bintray plugin?

[ilmat192]

Hi @eyalbe4! This issue prevents publishing Kotlin multiplatform libraries to Bintray but the PR mentioned above can fix it. Do you have any plans to merge it?

[fluidsonic]

Workaround which works for us until the Bintray plugin catches up.

build.gradle.kts

tasks.withType<BintrayUploadTask> {
    doFirst {
        publishing.publications
            .filterIsInstance<MavenPublication>()
            .forEach { publication ->
                val moduleFile = buildDir.resolve("publications/${publication.name}/module.json")
                if (moduleFile.exists()) {
                    publication.artifact(object : FileBasedMavenArtifact(moduleFile) {
                        override fun getDefaultExtension() = "module"
                    })
                }
            }
    }
}

Note that we use Gradle Kotlin Script, so for Grovvy-based build.gradle files the code needs to be adjusted.

[dhakehurst]

This is a great workaround, though how do you 'get' the 'publishing' variable

In my multi project, multiplatform build, in the root project 'publishing' is an unresolved reference!

[dhakehurst]

found the answer,
val publishing = extensions.getByType(PublishingExtension::class.java)

[ljacomet]

Finding this issue after having added a similar support to the build-info plugin for Artifactory integration.
@eyalbe4 If I open a PR to enable this plugin, in a similar manner to what was done in jfrog/build-info#265 (and follow up PRs), what would be the objective in terms of supported Gradle versions?
The current version of this build uses Gradle 4.3. It would be awesome to be able to bump this to at least 4.10.3 and leverage some of the APIs introduced on internal types in the 4.x line, not available in 4.3.