https://github.com/maxmind/GeoIP2-java

Java API for GeoIP2 webservice client and database reader
https://github.com/maxmind/GeoIP2-java

geoip geoip2 maxmind mmdb

Last synced: about 1 month ago
JSON representation

Java API for GeoIP2 webservice client and database reader

• Host: GitHub
• URL: https://github.com/maxmind/GeoIP2-java
• Owner: maxmind
• License: apache-2.0
• Created: 2013-04-01T21:40:11.000Z (over 11 years ago)
• Default Branch: main
• Last Pushed: 2024-11-13T23:08:41.000Z (about 1 month ago)
• Last Synced: 2024-11-19T19:07:38.914Z (about 1 month ago)
• Topics: geoip, geoip2, maxmind, mmdb
• Language: Java
• Homepage: https://maxmind.github.io/GeoIP2-java/
• Size: 5.76 MB
• Stars: 784
• Watchers: 62
• Forks: 204
• Open Issues: 2
• Metadata Files:
  • Readme: README.dev.md
  • Changelog: CHANGELOG.md
  • License: LICENSE

Awesome Lists containing this project

README

        
There is a release script at `dev-bin/release.sh` that will do the full

release, including updating the GitHub Pages site.

This script reads the VERSION number from `CHANGELOG.md`, which you should

have updated to contain the new version number and today's date. After

uploading with this script, you will need to perform the release on the

[Sonatype OSS site](https://oss.sonatype.org/index.html).

We release to the Maven Central Repository through Sonatype OSSRH. They

provide [detailed directions](https://central.sonatype.org/pages/apache-maven.html)

on the steps of the release or snapshot release process.

All releases should follow [Semantic Versioning](https://semver.org/).

Steps for releasing:

1. Review open issues and PRs to see if any can easily be fixed, closed, or

   merged.

2. Bump copyright year in `README.md`, if necessary.

   * You do not need to update the version. The release script will do so.

3. Review `CHANGELOG.md` for completeness and correctness. Update its release

   date. Commit it.

4. Install or update [gh](https://github.com/cli/cli) as it used by the release script.

5. Test that `mvn package` can complete successfully. Run `git clean -dxff`

   or something similar to clean up afterwards.

6. Run `./dev-bin/release.sh`.

   * This will package the release, update the gh-pages branch, bump the

     version to the next development release, upload the release to GitHub

     and tag it, and upload to Sonatype.

   * It may prompt you about out of date dependencies. You should consider

     updating them if appropriate. Say no and review the changes and upate

     `pom.xml` and start the release process over again if you do.

7. The `nexus-staging-maven-plugin` will automatically promote the release on Sonatype.

There is more information in the

[minfraud-api-java](https://github.com/maxmind/minfraud-api-java/blob/main/README.dev.md)

`README.dev.md` about doing a Java release, including setting up your

environment and completing the release on Sonatype.