It is strongly recommended that you choose a build system that supports dependency management, and one that can consume artifacts published to the “Maven Central” repository. We would recommend that you choose Maven or Gradle. It is possible to get Spring Boot to work with other build systems (Ant for example), but they will not be particularly well supported.
Maven users can inherit from the spring-boot-starter-parent
project to obtain sensible
defaults. The parent project provides the following features:
<version>
tags for common
dependencies, inherited from the spring-boot-dependencies
POM.To configure your project to inherit from the spring-boot-starter-parent
simply set
the parent
:
<!-- Inherit defaults from Spring Boot --> <parent> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter-parent</artifactId> <version>1.1.12.RELEASE</version> </parent>
![]() | Note |
---|---|
You should only need to specify the Spring Boot version number on this dependency. If you import additional starters, you can safely omit the version number. |
Not everyone likes inheriting from the spring-boot-starter-parent
POM. You may have your
own corporate standard parent that you need to use, or you may just prefer to explicitly
declare all your Maven configuration.
If you don’t want to use the spring-boot-starter-parent
, you can still keep the benefit
of the dependency management (but not the plugin management) by using a scope=import
dependency:
<dependencyManagement> <dependencies> <dependency> <!-- Import dependency management from Spring Boot --> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-dependencies</artifactId> <version>1.1.12.RELEASE</version> <type>pom</type> <scope>import</scope> </dependency> </dependencies> </dependencyManagement>
The spring-boot-starter-parent
chooses fairly conservative Java compatibility. If you
want to follow our recommendation and use a later Java version you can add a
java.version
property:
<properties> <java.version>1.8</java.version> </properties>
Spring Boot includes a Maven plugin
that can package the project as an executable jar. Add the plugin to your <plugins>
section if you want to use it:
<build> <plugins> <plugin> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-maven-plugin</artifactId> </plugin> </plugins> </build>
![]() | Note |
---|---|
If you use the Spring Boot starter parent pom, you only need to add the plugin, there is no need for to configure it unless you want to change the settings defined in the parent. |
Gradle users can directly import “starter POMs” in their dependencies
section. Unlike
Maven, there is no “super parent” to import to share some configuration.
apply plugin: 'java' repositories { mavenCentral() } dependencies { compile("org.springframework.boot:spring-boot-starter-web:1.1.12.RELEASE") }
The spring-boot-gradle-plugin
is also available and provides tasks to create executable jars and run projects from
source. It also adds a ResolutionStrategy
that enables you to
omit the version number
for “blessed” dependencies:
buildscript { repositories { mavenCentral() } dependencies { classpath("org.springframework.boot:spring-boot-gradle-plugin:1.1.12.RELEASE") } } apply plugin: 'java' apply plugin: 'spring-boot' repositories { mavenCentral() } dependencies { compile("org.springframework.boot:spring-boot-starter-web") testCompile("org.springframework.boot:spring-boot-starter-test") }
It is possible to build a Spring Boot project using Apache Ant, however, no special support or plugins are provided. Ant scripts can use the Ivy dependency system to import starter POMs.
See the Section 68.8, “Build an executable archive with Ant” “How-to” for more complete instructions.
Starter POMs are a set of convenient dependency descriptors that you can include in your
application. You get a one-stop-shop for all the Spring and related technology that you
need, without having to hunt through sample code and copy paste loads of dependency
descriptors. For example, if you want to get started using Spring and JPA for database
access, just include the spring-boot-starter-data-jpa
dependency in your project, and
you are good to go.
The starters contain a lot of the dependencies that you need to get a project up and running quickly and with a consistent, supported set of managed transitive dependencies.
The following application starters are provided by Spring Boot under the
org.springframework.boot
group:
Table 12.1. Spring Boot application starters
Name | Description |
---|---|
| The core Spring Boot starter, including auto-configuration support, logging and YAML. |
| Support for the “Advanced Message Queuing Protocol” via |
| Support for aspect-oriented programming including |
| Support for “Spring Batch” including HSQLDB database. |
| Support for the Elasticsearch search and analytics engine including
|
| Support for the GemFire distributed data store including |
| Support for the “Java Persistence API” including |
| Support for the MongoDB NoSQL Database, including |
| Support for exposing Spring Data repositories over REST via |
| Support for the Apache Solr search platform, including |
| Support for the FreeMarker templating engine |
| Support for the Groovy templating engine |
| Support for “Java Message Service API” via HornetQ. |
| Support for common |
| JDBC Database support. |
| Support for |
| Support for the REDIS key-value data store, including |
| Support for |
| Support for |
| Support for |
| Support for |
| Support for common test dependencies, including JUnit, Hamcrest and Mockito along with
the |
| Support for the Thymeleaf templating engine, including integration with Spring. |
| Support for the Velocity templating engine |
| Support for full-stack web development, including Tomcat and |
| Support for websocket development with Tomcat. |
| Support for Spring Web Services |
In addition to the application starters, the following starters can be used to add production ready features.
Table 12.2. Spring Boot production ready starters
Name | Description |
---|---|
| Adds production ready features such as metrics and monitoring. |
| Adds remote |
Finally, Spring Boot includes some starters that can be used if you want to exclude or swap specific technical facets.
Table 12.3. Spring Boot technical starters
Name | Description |
---|---|
| Imports the Jetty HTTP engine (to be used as an alternative to Tomcat) |
| Support the Log4J logging framework |
| Import Spring Boot’s default logging framework (Logback). |
| Import Spring Boot’s default HTTP engine (Tomcat). |
![]() | Tip |
---|---|
For a list of additional community contributed starter POMs, see the
README file in the
|