-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add badge for gradle plugin portal #1125
Comments
Hi, thanks for the suggestion. Do they have a public API? |
I can't find one 😞 |
I'm marking all the needs-upstream-help issues closed. If there's new information from the upstream service, please post in the thread. If they're actionable by Shields, a maintainer will reopen the issue. If anyone wants to follow up with these vendors, feel free to do that! Even though the unresolved issues are closed, they are easy to find: https://github.com/badges/shields/issues?q=label%3Aneeds-upstream-help+is%3Aclosed |
In the meantime, can't we just parse the output of |
Shields has limited server resources so we avoid parsing HTML for performance reasons. Wanted to link gradle/gradle#1477 which is the request for an API. |
Actually I think this can be solved by the maven-metadata badges, I need to play around with that though. |
Just for reference: |
With the maven repo https://plugins.gradle.org/m2/ and the Maven metadata URL it work for me.
|
As suggested here: badges/shields#1125 (comment)
As suggested here: badges/shields#1125 (comment)
@paulmelnikow Can you/we add the Gradle Plugin Portal badge as an alias of #1125 (comment)? The plugin marker artifact's group id is the id of the plugin and artifact id is |
It would be cool if we have a badge for the gradle plugin portal.
I image it like similar the maven central or the bintray badge.
(If it's working of course 🙃)
plugin portal | v0.9.95
You can use this URL for example: (don't know how shields works, but I think you need that 😄)
https://plugins.gradle.org/plugin/org.shipkit.java-publish/0.9.95
The text was updated successfully, but these errors were encountered: