spring-http-exception-handling-library-client
Used in:
components
- OverviewOverview
- VersionsVersions
- DependentsDependents
- DependenciesDependencies
<dependency>
<groupId>io.github.lsd-consulting</groupId>
<artifactId>spring-http-exception-handling-library-client</artifactId>
<version>2.0.6</version>
</dependency><?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<!-- This module was also published with a richer model, Gradle metadata, -->
<!-- which should be used instead. Do not delete the following line which -->
<!-- is to indicate to Gradle or any Gradle module metadata file consumer -->
<!-- that they should prefer consuming it instead. -->
<!-- do_not_remove: published-with-gradle-metadata -->
<modelVersion>4.0.0</modelVersion>
<groupId>io.github.lsd-consulting</groupId>
<artifactId>spring-http-exception-handling-library-client</artifactId>
<version>2.0.6</version>
<name>Spring Http Exception Handling Library - client</name>
<description>A set of Spring exception handlers making sure the application always returns a consistent error response.</description>
<url>https://github.com/lsd-consulting/spring-http-exception-handling-library</url>
<licenses>
<license>
<name>MIT License</name>
<url>https://github.com/lsd-consulting/spring-http-exception-handling-library/blob/main/LICENSE.txt</url>
<distribution>repo</distribution>
</license>
</licenses>
<developers>
<developer>
<name>Lukasz</name>
<email>lukasz.gryzbon@gmail.com</email>
<organization>Integreety Ltd.</organization>
<organizationUrl>https://www.integreety.co.uk</organizationUrl>
</developer>
<developer>
<name>Nick</name>
<email>nicholas.mcdowall@gmail.com</email>
<organization>NKM IT Solutions</organization>
<organizationUrl>https://github.com/nickmcdowall</organizationUrl>
</developer>
</developers>
<scm>
<url>https://github.com/lsd-consulting/spring-http-exception-handling-library.git</url>
</scm>
<dependencies>
<dependency>
<groupId>org.jetbrains.kotlin</groupId>
<artifactId>kotlin-stdlib</artifactId>
<version>2.1.21</version>
<scope>compile</scope>
</dependency>
<dependency>
<groupId>io.github.lsd-consulting</groupId>
<artifactId>spring-http-exception-handling-library-api</artifactId>
<version>2.0.6</version>
<scope>runtime</scope>
</dependency>
<dependency>
<groupId>io.github.lsd-consulting</groupId>
<artifactId>lsd-logging-library</artifactId>
<version>1.0.18</version>
<scope>runtime</scope>
</dependency>
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-web</artifactId>
<scope>runtime</scope>
</dependency>
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-validation</artifactId>
<scope>runtime</scope>
</dependency>
<dependency>
<groupId>org.springframework.cloud</groupId>
<artifactId>spring-cloud-starter-openfeign</artifactId>
<scope>runtime</scope>
</dependency>
<dependency>
<groupId>com.fasterxml.jackson.datatype</groupId>
<artifactId>jackson-datatype-jsr310</artifactId>
<version>2.17.2</version>
<scope>runtime</scope>
</dependency>
</dependencies>
<dependencyManagement>
<dependencies>
<dependency>
<groupId>org.jetbrains.kotlin</groupId>
<artifactId>kotlin-bom</artifactId>
<version>2.1.21</version>
<scope>import</scope>
<type>pom</type>
</dependency>
<dependency>
<groupId>org.springframework.cloud</groupId>
<artifactId>spring-cloud-dependencies</artifactId>
<version>2023.0.5</version>
<scope>import</scope>
<type>pom</type>
</dependency>
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-dependencies</artifactId>
<version>3.2.12</version>
<scope>import</scope>
<type>pom</type>
</dependency>
</dependencies>
</dependencyManagement>
</project>
Open source consumption has exploded, with estimates placing this year’s downloads at over 6.6 trillion. This reliance on open source components, now making up to 90% of the modern software application, has ushered in both unprecedented innovation and complex challenges for software supply chains.
View the Report