Gradle Plugins on Maven Central fail to resolve #44967
Unanswered
veyndan
asked this question in
Request Help
Replies: 2 comments 1 reply
|
Ah, interesting! In which case, yes we can re-add this plugin for lookup. As you may have seen from that discussion, we intentionally try not to look up Are you aware of any other Gradle Plugins you use that are on Maven Central? |
1 reply
|
I suspect the problem in this case elsewhere. https://plugins.gradle.org/plugin/org.jetbrains.kotlin.plugin.compose/2.0.20 (and other versions) exist in plugins.gradle.org and this domain is added to the list of lookup sources by default (analogous to what gradle does). A quick test without any further config presented me with an update. [versions]
kotlin = "2.0.20"
[plugins]
jetbrainsComposeCompiler = { id = "org.jetbrains.kotlin.plugin.compose", version.ref = "kotlin" } -> |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
How are you running Renovate?
A Mend.io-hosted app
Which platform you running Renovate on?
GitHub.com
Which version of Renovate are you using?
44.3.2
Please tell us more about your question or problem
Renovate incorrectly skips searching for Gradle plugins in Maven Central. For example, we depend on
org.jetbrains.kotlin.plugin.compose:org.jetbrains.kotlin.plugin.compose.gradle.pluginin ourbuild-logicas acompileOnlydependency for use by our convention plugins.This discussion raised a similar point, but has since been locked. I don't believe that the point about looking up Gradle Plugins from Maven Central is correct. It's completely valid to look them up from Maven Central when developing convention plugins. The aforementioned plugin is indeed published to Maven Central, so it follows that they are usable from Maven Central (as we've successfully been doing when building, despite what Renovate says).
Logs (if relevant)
Logs
All reactions