Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Gradle plugins register/portal is not in sync with GitHub releases

See original GitHub issue

Somehow the last released version in the Gradle plugins portal/register is 0.13.2-rc.4 (which is not even in GitHub as far as I can tell). The last release in GitHub is 0.16.1.

I think most people will use the Gradle portal before coming to GitHub. Not sure how anything gets into that portal, but somehow something in not in sync with it.

Issue Analytics

State:
Created a year ago
Comments:5 (2 by maintainers)

Top GitHub Comments

1reaction

x80486commented, Mar 27, 2022

OK, great. I just didn’t know if you were aware of that — or not. I can close this one 😎

0reactions

ajoberstarcommented, Mar 27, 2022

Right, the portal UI will not show that newer versions of the plugin are available. That requires the API incantations that the com.gradle.plugin-publish plugin does. However, the plugin portal repo proxies JCenter and Maven Central, so anything available in those two is available without extra configuration in your build.

For example, this URL will download the 0.16.1 POM, even though in the UI it doesn’t look like it’s available.

https://plugins.gradle.org/m2/org/ajoberstar/reckon/reckon-gradle/0.16.1/reckon-gradle-0.16.1.pom

This means that you do not need to customize your pluginManagement.repositories to get the latest version of reckon.

I understand that it can be confusing for a user that the latest version isn’t indicated in the portal UI, but the reasons outlined in that grgit issue override that convenience for me as a maintainer.

Top Results From Across the Web

Can't resolve plugins from plugin repository after Gradle 4.3 ...

Expected Behavior When running my build, plugins declared in the plugins closure should be resolved from the Gradle Plugins Repository.

BreadMoirai/github-release-gradle-plugin

This plugin is not endorsed by Github. This plugin uses OkHttp to send a POST requests to the github api that creates a...

Gradle Release Plugin - GitHub

gradle -release is a plugin for providing a Maven-like release process for projects using Gradle - GitHub - researchgate/gradle-release: gradle-release is a ...

AppSync Gradle Plugin Not Compatible with Gradle 6 #270

When I add: apply plugin: 'com.amazonaws.appsync' to my app's build.gradle I get this error when I sync: Caused by: ...

Option not to push tags to a git repo on a release #68 - GitHub

We'd like to forego pushing the tags in certain types of releases while still specifying a version using -Prelease.version= , e.g. ./gradlew - ......