https://kotlinlang.org logo
Title
r

René

03/05/2019, 7:47 AM
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
k

karelpeeters

03/05/2019, 9:57 AM
#gradle
m

Mike

03/05/2019, 11:13 AM
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.
r

René

03/05/2019, 12:30 PM
Okay, sorry for this false report. (their solution does not work so I was looking for the reason where this comes from)
t

toto

03/06/2019, 8:48 AM
@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
r

René

03/06/2019, 8:50 AM
I already found a possible patch as mentioned in the latest comment
t

toto

03/06/2019, 8:51 AM
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 👍
I have seen the last message from this morning @René that is what I intended to try. Feel free to open a PR against
develop
r

René

03/07/2019, 8:51 AM
FYI: PR is open
t

toto

03/07/2019, 9:45 AM
Thanks @René, I will take a look asap