Hey guys, I run into trouble while publishing a project. I am not absolutely sure, but I guess I found a bug in the kotlin gradle plugin. For some strange reasons there is a "maven" publication from nowhere. I think the kotlin plugin might create that one. For now I just found a reference in MPP, but I think there is also something for "normal" projects. Is there someone familiar with the gradle plugin? I already opened a bug on a differnt project for more details check this link: https://github.com/novoda/bintray-release/issues/266

Reading thread, and responses, it appears there’s an issue with the bintray release plugin, and they’ve provided a workaround I don’t think this is related to the Kotlin plugin.

Okay, sorry for this false report. (their solution does not work so I was looking for the reason where this comes from)

@René as mentioned in GH and in the Gradle slack, that

maven

publication is not coming from nowhere, but created by the plugin you are applying. If the

novoda/bintray-release

plugin is not working for your scenario consider to use directly the

bintray/gradle-bintray-plugin

instead, as our plugin is just configuring the other one. https://github.com/bintray/gradle-bintray-plugin

I already found a possible patch as mentioned in the latest comment

that way of creating the pom - as mentioned in that thread - has some issues with collecting correctly transitive dependencies, but if that works for you then 👍

FYI: PR is open

Thanks @René, I will take a look asap