spring-boot/spring-boot-project/spring-boot-starters/spring-boot-starter-validation/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-validation</artifactId>
	<name>Spring Boot Validation Starter</name>
	<description>Starter for using Java Bean Validation with Hibernate
		Validator</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>jakarta.validation</groupId>
			<artifactId>jakarta.validation-api</artifactId>
		</dependency>
		<dependency>
			<groupId>org.apache.tomcat.embed</groupId>
			<artifactId>tomcat-embed-el</artifactId>
		</dependency>
		<dependency>
			<groupId>org.hibernate.validator</groupId>
			<artifactId>hibernate-validator</artifactId>
			<exclusions>
				<exclusion>
					<groupId>javax.validation</groupId>
					<artifactId>validation-api</artifactId>
				</exclusion>
			</exclusions>
		</dependency>
	</dependencies>
</project>
Introduce a validation starter Previously, the only starter that provided validation was spring-boot-starter-web which included Hibernate Validator and Tomcat's EL implementation. This left users writing non-web applications to figure out the dependencies for themselves. They would sometimes run into difficulties as Hibernate Validator's need for an EL implementation would trip them up. This commit adds a new starter, spring-boot-starter-validation, which provides both Hibernate Validator and Tomcat's EL implementation. spring-boot-starter-web has been updated to depend on this starter rather than depending on Hibernate Validator directly. Closes gh-2678 10 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">`
Introduce a validation starter Previously, the only starter that provided validation was spring-boot-starter-web which included Hibernate Validator and Tomcat's EL implementation. This left users writing non-web applications to figure out the dependencies for themselves. They would sometimes run into difficulties as Hibernate Validator's need for an EL implementation would trip them up. This commit adds a new starter, spring-boot-starter-validation, which provides both Hibernate Validator and Tomcat's EL implementation. spring-boot-starter-web has been updated to depend on this starter rather than depending on Hibernate Validator directly. Closes gh-2678 10 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>`
Introduce a validation starter Previously, the only starter that provided validation was spring-boot-starter-web which included Hibernate Validator and Tomcat's EL implementation. This left users writing non-web applications to figure out the dependencies for themselves. They would sometimes run into difficulties as Hibernate Validator's need for an EL implementation would trip them up. This commit adds a new starter, spring-boot-starter-validation, which provides both Hibernate Validator and Tomcat's EL implementation. spring-boot-starter-web has been updated to depend on this starter rather than depending on Hibernate Validator directly. Closes gh-2678 10 years ago			`</parent>`
			`<artifactId>spring-boot-starter-validation</artifactId>`
			`<name>Spring Boot Validation Starter</name>`
Auto-generate tables describing the first-party starters Previously, the documentation included hand-written tables for the application, production, and technical starters. This commit replaces the hand-written tables with tables that are generated automatically from all of the starter poms, thereby ensuring that the documentation is automatically kept up-to-date as starters are added and removed. An extra column provided a link to each starter's pom on GitHub has also been added to the table. This makes it easier for users to see exactly what each starter contains. Closes gh-5267 9 years ago			`<description>Starter for using Java Bean Validation with Hibernate`
			`Validator</description>`
Introduce a validation starter Previously, the only starter that provided validation was spring-boot-starter-web which included Hibernate Validator and Tomcat's EL implementation. This left users writing non-web applications to figure out the dependencies for themselves. They would sometimes run into difficulties as Hibernate Validator's need for an EL implementation would trip them up. This commit adds a new starter, spring-boot-starter-validation, which provides both Hibernate Validator and Tomcat's EL implementation. spring-boot-starter-web has been updated to depend on this starter rather than depending on Hibernate Validator directly. Closes gh-2678 10 years ago			`<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>`
Introduce a validation starter Previously, the only starter that provided validation was spring-boot-starter-web which included Hibernate Validator and Tomcat's EL implementation. This left users writing non-web applications to figure out the dependencies for themselves. They would sometimes run into difficulties as Hibernate Validator's need for an EL implementation would trip them up. This commit adds a new starter, spring-boot-starter-validation, which provides both Hibernate Validator and Tomcat's EL implementation. spring-boot-starter-web has been updated to depend on this starter rather than depending on Hibernate Validator directly. Closes gh-2678 10 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>`
Introduce a validation starter Previously, the only starter that provided validation was spring-boot-starter-web which included Hibernate Validator and Tomcat's EL implementation. This left users writing non-web applications to figure out the dependencies for themselves. They would sometimes run into difficulties as Hibernate Validator's need for an EL implementation would trip them up. This commit adds a new starter, spring-boot-starter-validation, which provides both Hibernate Validator and Tomcat's EL implementation. spring-boot-starter-web has been updated to depend on this starter rather than depending on Hibernate Validator directly. Closes gh-2678 10 years ago			`<dependencies>`
			`<dependency>`
			`<groupId>org.springframework.boot</groupId>`
			`<artifactId>spring-boot-starter</artifactId>`
			`</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>`
			`<groupId>jakarta.validation</groupId>`
			`<artifactId>jakarta.validation-api</artifactId>`
			`</dependency>`
Introduce a validation starter Previously, the only starter that provided validation was spring-boot-starter-web which included Hibernate Validator and Tomcat's EL implementation. This left users writing non-web applications to figure out the dependencies for themselves. They would sometimes run into difficulties as Hibernate Validator's need for an EL implementation would trip them up. This commit adds a new starter, spring-boot-starter-validation, which provides both Hibernate Validator and Tomcat's EL implementation. spring-boot-starter-web has been updated to depend on this starter rather than depending on Hibernate Validator directly. Closes gh-2678 10 years ago			`<dependency>`
			`<groupId>org.apache.tomcat.embed</groupId>`
			`<artifactId>tomcat-embed-el</artifactId>`
			`</dependency>`
			`<dependency>`
Upgrade to Hibernate Validator 6.0.2.Final Closes gh-9969 7 years ago			`<groupId>org.hibernate.validator</groupId>`
Introduce a validation starter Previously, the only starter that provided validation was spring-boot-starter-web which included Hibernate Validator and Tomcat's EL implementation. This left users writing non-web applications to figure out the dependencies for themselves. They would sometimes run into difficulties as Hibernate Validator's need for an EL implementation would trip them up. This commit adds a new starter, spring-boot-starter-validation, which provides both Hibernate Validator and Tomcat's EL implementation. spring-boot-starter-web has been updated to depend on this starter rather than depending on Hibernate Validator directly. Closes gh-2678 10 years ago			`<artifactId>hibernate-validator</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>`
			`<groupId>javax.validation</groupId>`
			`<artifactId>validation-api</artifactId>`
			`</exclusion>`
			`</exclusions>`
Introduce a validation starter Previously, the only starter that provided validation was spring-boot-starter-web which included Hibernate Validator and Tomcat's EL implementation. This left users writing non-web applications to figure out the dependencies for themselves. They would sometimes run into difficulties as Hibernate Validator's need for an EL implementation would trip them up. This commit adds a new starter, spring-boot-starter-validation, which provides both Hibernate Validator and Tomcat's EL implementation. spring-boot-starter-web has been updated to depend on this starter rather than depending on Hibernate Validator directly. Closes gh-2678 10 years ago			`</dependency>`
			`</dependencies>`
			`</project>`