This message was deleted.
# plugin-development
s
This message was deleted.
t
I am publishing several libraries to Maven Central, which my plugin depends on, yes
👌 1
Gradle Plugin Portal only supports plugins per se
e
Thanks @tony good to see you here 🙂
👋 1
m
if I have a library with artifacts published to maven central and now i want to add a gradle plugin, should I publish this plugin to Gradle Plugin Portal or is Maven Central fine?
e
I guess that’s up to you, but I prefer to publish it to Gradle Plugin Portal so it can be searched as well
m
that's what I'm wondering, what are the advantages and disadvantages of both. I think there are some configuration workarounds for android plugins which are not published to gradle plugin portal and thus not fully compatible with `pluginManagement`https://stefma.medium.com/its-time-to-ditch-the-buildscript-block-a1ab12e0d9ce.
t
I'm not sure what you mean by "android plugins". I publish my plugin to both the portal and central.
if you're referring to the Android family of plugins published by Google (AGP), they're all fully compatible with pluginManagement for a while
✅ 1
m
yes, those. I checked a few months ago and it was a problem, good to know it's all fine now, thank you 🙂
t
since like 4.2 I think
m
no way 😼 maybe I'm talking about something else or I missed something, I just checked and I used a workaround on 11/2021 with 7.1.1 for
com.android.tools.build:gradle
. And hilt has definitely been only fixed on february (it's a different source, though)
seems like it was still relevant in dec 2021. whatever, though, it's important it's fine now and I wasn't aware 😉
t
maybe Hilt is different, I don't use it. I've been using the "modern" approach for the core plugins for a long time now, though