Error Handling Spring Boot Starter

Table of Contents

• Goal
• Documentation
• Spring Boot compatibility
• Articles
• Release

Goal

The goal of the project is to make it easy to have proper and consistent error responses for REST APIs build with Spring Boot.

Documentation

See https://wimdeblauwe.github.io/error-handling-spring-boot-starter for the extensive documentation.

If you are new to the library, check out Better Error Handling for Your Spring Boot REST APIs for an introductory overview.

ℹ️	Documentation is very important to us, so if you find something missing from the docs, please create an issue about it.

Spring Boot compatibility

error-handling-spring-boot-starter	Spring Boot	Minimum Java version	Docs
4.5.0	3.3.x	17	Documentation 4.5.0
4.4.0	3.3.x	17	Documentation 4.4.0
4.3.0	3.x	17	Documentation 4.3.0
4.2.0	3.x	17	Documentation 4.2.0
4.1.3	3.x	17	Documentation 4.1.3
4.0.0	3.0.x	17	Documentation 4.0.0
3.4.1	2.7.x	11	Documentation 3.4.1
3.3.0	2.7.x	11	Documentation 3.3.0
3.2.0	2.5.x	11	N/A
2.1.0	2.5.x	11	N/A

Articles

Blogs and articles about this library:

• Better Error Handling for Your Spring Boot REST APIs - Nice article on foojay.io that explains the library in detail

• Error Handling Spring Boot Starter release 1.6.0 - Blog post explaining the updates in version 1.6.0

• Error handling library for Spring Boot - Original blog post that introduced the library

Release

To release a new version of the project, follow these steps:

1. Update pom.xml with the new version (Use mvn versions:set -DgenerateBackupPoms=false -DnewVersion=<VERSION>)

2. Commit the changes locally.

3. Tag the commit with the version (e.g. 1.0.0) and push the tag.

4. Create a new release in GitHub via https://github.com/wimdeblauwe/error-handling-spring-boot-starter/releases/new

   • Select the newly pushed tag

   • Update the release notes. This should automatically start the [release action](https://github.com/wimdeblauwe/error-handling-spring-boot-starter/actions).

5. Merge the tag to master so the documentation is updated.

6. Update pom.xml again with the next SNAPSHOT version.

7. Close the milestone in the GitHub issue tracker.