Description

<dependency>
    <groupId>dev.jbaby</groupId>
    <artifactId>wicket-spring-boot-starter</artifactId>
    <version>0.1.0</version>
</dependency>

<?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 http://maven.apache.org/xsd/maven-4.0.0.xsd">

	<modelVersion>4.0.0</modelVersion>

	<parent>
		<groupId>dev.jbaby</groupId>
		<artifactId>wicket-spring-boot-starter-parent</artifactId>
		<version>0.1.0</version>
		<relativePath>../pom.xml</relativePath>
	</parent>

	<artifactId>wicket-spring-boot-starter</artifactId>
	<packaging>jar</packaging>

	<name>Wicket Spring Boot Starter</name>
	<description>
		Lightweight auto-configuration and integration starter for Apache Wicket and Spring Boot.
	</description>

	<properties>
		<!-- Default for the invoker's skipInvocation, so -DskipTests skips the integration tests too -->
		<skipTests>false</skipTests>
	</properties>

	<dependencies>
		<!-- Wicket Core and Spring Integration -->
		<dependency>
			<groupId>org.apache.wicket</groupId>
			<artifactId>wicket-core</artifactId>
		</dependency>
		<dependency>
			<groupId>org.apache.wicket</groupId>
			<artifactId>wicket-spring</artifactId>
			<exclusions>
				<exclusion>
					<groupId>org.springframework</groupId>
					<artifactId>spring-core</artifactId>
				</exclusion>
				<exclusion>
					<groupId>org.springframework</groupId>
					<artifactId>spring-beans</artifactId>
				</exclusion>
				<exclusion>
					<groupId>org.springframework</groupId>
					<artifactId>spring-context</artifactId>
				</exclusion>
				<exclusion>
					<groupId>org.springframework</groupId>
					<artifactId>spring-web</artifactId>
				</exclusion>
			</exclusions>
		</dependency>

		<!-- Spring Boot AutoConfigure and Starter dependencies (versions managed by the
		     spring-boot-dependencies BOM imported in the parent pom) -->
		<dependency>
			<groupId>org.springframework.boot</groupId>
			<artifactId>spring-boot-autoconfigure</artifactId>
		</dependency>
		<!-- Brings the embedded servlet container and web infrastructure Wicket needs.
		     Without it an application depending only on this starter would boot as a
		     non-web application, and the auto-configuration would never activate.
		     spring-boot-starter-web is deprecated as of Spring Boot 4 in favour of this. -->
		<dependency>
			<groupId>org.springframework.boot</groupId>
			<artifactId>spring-boot-starter-webmvc</artifactId>
		</dependency>
		<dependency>
			<groupId>org.springframework.boot</groupId>
			<artifactId>spring-boot-configuration-processor</artifactId>
			<optional>true</optional>
		</dependency>
		<!-- Writes META-INF/spring-autoconfigure-metadata.properties, which lets Spring Boot evaluate
		     the auto-configuration's class conditions at startup without loading its classes. -->
		<dependency>
			<groupId>org.springframework.boot</groupId>
			<artifactId>spring-boot-autoconfigure-processor</artifactId>
			<optional>true</optional>
		</dependency>

		<!-- Test dependencies -->
		<dependency>
			<groupId>org.springframework.boot</groupId>
			<artifactId>spring-boot-starter-test</artifactId>
			<scope>test</scope>
		</dependency>
		<dependency>
			<groupId>org.apache.wicket</groupId>
			<artifactId>wicket-tester</artifactId>
			<scope>test</scope>
		</dependency>
		<!-- WebApplicationContextRunner (used to test WicketAutoConfiguration) needs
		     spring-web's ConfigurableWebApplicationContext, which isn't pulled in
		     transitively: spring-boot-autoconfigure's dependencies are all optional, and
		     wicket-spring excludes spring-web above. -->
		<dependency>
			<groupId>org.springframework</groupId>
			<artifactId>spring-web</artifactId>
			<scope>test</scope>
		</dependency>
	</dependencies>

	<build>
		<plugins>
			<!-- Builds the projects under src/it against the freshly built starter. They inherit from
			     spring-boot-starter-parent rather than from this build, so they consume the starter
			     exactly the way a user's application does: through its published pom alone. -->
			<plugin>
				<groupId>org.apache.maven.plugins</groupId>
				<artifactId>maven-invoker-plugin</artifactId>
				<configuration>
					<cloneProjectsTo>${project.build.directory}/it</cloneProjectsTo>
					<localRepositoryPath>${project.build.directory}/local-repo</localRepositoryPath>
					<settingsFile>src/it/settings.xml</settingsFile>
					<pomIncludes>
						<pomInclude>*/pom.xml</pomInclude>
					</pomIncludes>
					<goals>
						<goal>verify</goal>
					</goals>
					<!-- Passed explicitly so that -Dspring-boot.version=... on the command line also
					     reaches the test projects (the invoker otherwise filters with the pom's value). -->
					<filterProperties>
						<spring-boot.version>${spring-boot.version}</spring-boot.version>
					</filterProperties>
					<showErrors>true</showErrors>
					<skipInvocation>${skipTests}</skipInvocation>
				</configuration>
				<executions>
					<execution>
						<id>integration-test</id>
						<goals>
							<goal>install</goal>
							<goal>run</goal>
						</goals>
					</execution>
				</executions>
			</plugin>
		</plugins>
	</build>
</project>