spring-boot/spring-boot-project/spring-boot-starters/spring-boot-starter-webflux/pom.xml

<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd">
	<modelVersion>4.0.0</modelVersion>
	<parent>
		<groupId>org.springframework.boot</groupId>
		<artifactId>spring-boot-starters</artifactId>
		<version>${revision}</version>
	</parent>
	<artifactId>spring-boot-starter-webflux</artifactId>
	<name>Spring Boot WebFlux Starter</name>
	<description>Starter for building WebFlux applications using Spring Framework's
		Reactive Web support</description>
	<properties>
		<main.basedir>${basedir}/../../..</main.basedir>
	</properties>
	<scm>
		<url>${git.url}</url>
		<connection>${git.connection}</connection>
		<developerConnection>${git.developerConnection}</developerConnection>
	</scm>
	<dependencies>
		<dependency>
			<groupId>org.springframework.boot</groupId>
			<artifactId>spring-boot-starter</artifactId>
		</dependency>
		<dependency>
			<groupId>org.springframework.boot</groupId>
			<artifactId>spring-boot-starter-json</artifactId>
		</dependency>
		<dependency>
			<groupId>org.springframework.boot</groupId>
			<artifactId>spring-boot-starter-reactor-netty</artifactId>
		</dependency>
		<dependency>
			<groupId>org.springframework.boot</groupId>
			<artifactId>spring-boot-starter-validation</artifactId>
			<exclusions>
				<exclusion>
					<groupId>org.apache.tomcat.embed</groupId>
					<artifactId>tomcat-embed-el</artifactId>
				</exclusion>
			</exclusions>
		</dependency>
		<dependency>
			<groupId>org.springframework</groupId>
			<artifactId>spring-web</artifactId>
		</dependency>
		<dependency>
			<groupId>org.springframework</groupId>
			<artifactId>spring-webflux</artifactId>
		</dependency>
		<dependency>
			<groupId>org.synchronoss.cloud</groupId>
			<artifactId>nio-multipart-parser</artifactId>
		</dependency>
	</dependencies>
</project>
Add Reactor Netty and WebFlux Starters These starters bring the Spring WebFlux experience to Boot. By default, the Reactor Netty web server is chosen. 8 years ago			`<?xml version="1.0" encoding="UTF-8"?>`
Fix POMs for the updated build/release process Fix POMs following project relocations and apply CI friendly Maven conventions. See gh-9316 8 years ago			`<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"`
Update build and setup configuration to use HTTPS See gh-16246 6 years ago			`xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd">`
Add Reactor Netty and WebFlux Starters These starters bring the Spring WebFlux experience to Boot. By default, the Reactor Netty web server is chosen. 8 years ago			`<modelVersion>4.0.0</modelVersion>`
			`<parent>`
			`<groupId>org.springframework.boot</groupId>`
			`<artifactId>spring-boot-starters</artifactId>`
Fix POMs for the updated build/release process Fix POMs following project relocations and apply CI friendly Maven conventions. See gh-9316 8 years ago			`<version>${revision}</version>`
Add Reactor Netty and WebFlux Starters These starters bring the Spring WebFlux experience to Boot. By default, the Reactor Netty web server is chosen. 8 years ago			`</parent>`
			`<artifactId>spring-boot-starter-webflux</artifactId>`
			`<name>Spring Boot WebFlux Starter</name>`
			`<description>Starter for building WebFlux applications using Spring Framework's`
			`Reactive Web support</description>`
			`<properties>`
Fix POMs for the updated build/release process Fix POMs following project relocations and apply CI friendly Maven conventions. See gh-9316 8 years ago			`<main.basedir>${basedir}/../../..</main.basedir>`
Add Reactor Netty and WebFlux Starters These starters bring the Spring WebFlux experience to Boot. By default, the Reactor Netty web server is chosen. 8 years ago			`</properties>`
Correct SCM URLs in published poms Previously, Maven's default behaviour was relied up which resulted in the artifact ID being appended to each URL as it was inherited. This behaviour can only be disabled in Maven 3.6 and later, a version that we cannot use due to an incompatibility with the Flatten Plugin. This commit works around Maven's default behaviour by defining properties for the SCM URL, connection, and developer connection and then explicitly defining the settings in each pom using these properties. The explicit definition of the properties in each pom prevents them being inherited from the parent, thereby disabling the unwanted appending of the artifact ID to the URL. Fixes gh-18328 5 years ago			`<scm>`
			`<url>${git.url}</url>`
			`<connection>${git.connection}</connection>`
			`<developerConnection>${git.developerConnection}</developerConnection>`
			`</scm>`
Add Reactor Netty and WebFlux Starters These starters bring the Spring WebFlux experience to Boot. By default, the Reactor Netty web server is chosen. 8 years ago			`<dependencies>`
Rework "Remove redundant spring-boot-starter dependency" This commit reworks 40d8726 as it has introduced an unfortunate side effect for those who are using a starter with optional starter dependencies. `spring-boot-starter-web` defines the json and the tomcat starter. The latter is part of a set of starters that do not bring the base starter and the former can be excluded to use gson rather than jackson. When such arrangement happens, spring-boot-starter-web no longer defines the base starter (and therefore doesn't bring the core dependencies that Spring Boot needs to bootstrap). This commit reviews the starters that define optional starters and reintroduce the base starter. Closes gh-14076 6 years ago			`<dependency>`
			`<groupId>org.springframework.boot</groupId>`
			`<artifactId>spring-boot-starter</artifactId>`
			`</dependency>`
Add Reactor Netty and WebFlux Starters These starters bring the Spring WebFlux experience to Boot. By default, the Reactor Netty web server is chosen. 8 years ago			`<dependency>`
			`<groupId>org.springframework.boot</groupId>`
Add json starter This commit adds a new json starter that gathers the core bits to read and write json with dedicated Java 8 extensions. The web-related starters have been improved to use the new starter rather than relying on `jackson-databind` directly. Closes gh-9297 8 years ago			`<artifactId>spring-boot-starter-json</artifactId>`
Add Reactor Netty and WebFlux Starters These starters bring the Spring WebFlux experience to Boot. By default, the Reactor Netty web server is chosen. 8 years ago			`</dependency>`
			`<dependency>`
Add json starter This commit adds a new json starter that gathers the core bits to read and write json with dedicated Java 8 extensions. The web-related starters have been improved to use the new starter rather than relying on `jackson-databind` directly. Closes gh-9297 8 years ago			`<groupId>org.springframework.boot</groupId>`
			`<artifactId>spring-boot-starter-reactor-netty</artifactId>`
Add Reactor Netty and WebFlux Starters These starters bring the Spring WebFlux experience to Boot. By default, the Reactor Netty web server is chosen. 8 years ago			`</dependency>`
Switch to Jakarta EE API dependencies where possible Closes gh-16113 Closes gh-16112 Closes gh-16111 Closes gh-15916 Closes gh-15689 6 years ago			`<dependency>`
Update WebFlux starter to depend on validation starter Previously, the WebFlux starter declared direct dependencies on Hibernate Validator and the Jakarta EE validation API. This meant that it required two exclusions to exclude validation from a reactive web application that did not need it. This commit updates the WebFlux starter to get its validation dependencies via a dependency on the validation starter. This allows validation to be excluded using a single exclusion. The EL dependency from the validation starter has been excluded to allow the EL implementation from the underlying container starter to continue to be used instead. See gh-16593 6 years ago			`<groupId>org.springframework.boot</groupId>`
			`<artifactId>spring-boot-starter-validation</artifactId>`
Switch to Jakarta EE API dependencies where possible Closes gh-16113 Closes gh-16112 Closes gh-16111 Closes gh-15916 Closes gh-15689 6 years ago			`<exclusions>`
			`<exclusion>`
Update WebFlux starter to depend on validation starter Previously, the WebFlux starter declared direct dependencies on Hibernate Validator and the Jakarta EE validation API. This meant that it required two exclusions to exclude validation from a reactive web application that did not need it. This commit updates the WebFlux starter to get its validation dependencies via a dependency on the validation starter. This allows validation to be excluded using a single exclusion. The EL dependency from the validation starter has been excluded to allow the EL implementation from the underlying container starter to continue to be used instead. See gh-16593 6 years ago			`<groupId>org.apache.tomcat.embed</groupId>`
			`<artifactId>tomcat-embed-el</artifactId>`
Switch to Jakarta EE API dependencies where possible Closes gh-16113 Closes gh-16112 Closes gh-16111 Closes gh-15916 Closes gh-15689 6 years ago			`</exclusion>`
			`</exclusions>`
Add Reactor Netty and WebFlux Starters These starters bring the Spring WebFlux experience to Boot. By default, the Reactor Netty web server is chosen. 8 years ago			`</dependency>`
			`<dependency>`
			`<groupId>org.springframework</groupId>`
			`<artifactId>spring-web</artifactId>`
			`</dependency>`
			`<dependency>`
			`<groupId>org.springframework</groupId>`
			`<artifactId>spring-webflux</artifactId>`
			`</dependency>`
Add synchronoss multipart dependency in webflux starter Fixes gh-17484 5 years ago			`<dependency>`
			`<groupId>org.synchronoss.cloud</groupId>`
			`<artifactId>nio-multipart-parser</artifactId>`
			`</dependency>`
Add Reactor Netty and WebFlux Starters These starters bring the Spring WebFlux experience to Boot. By default, the Reactor Netty web server is chosen. 8 years ago			`</dependencies>`
			`</project>`