This commit is contained in:
Stephane Nicoll
2019-01-29 15:25:34 +01:00
parent 0f53acc6bd
commit b60cbabb72
2 changed files with 153 additions and 150 deletions

View File

@@ -101,7 +101,8 @@ list of the available configuration options.
Here is the most basic dependency entry you could have
```yml
[source,yaml,indent=0]
----
initializr:
dependencies:
- name: Core
@@ -109,7 +110,7 @@ initializr:
- id: security
name: Security
description: Secure your application via spring-security
```
----
TIP: The `security` dependency is held within a group called "Core".
@@ -122,7 +123,8 @@ Let's now add a custom dependency that is not managed by Spring Boot and that on
work from Spring Boot `1.2.0.RELEASE` and onwards but should not be used in the 1.3
lines and further for some reason.
```yml
[source,yaml,indent=0]
----
initializr:
dependencies:
- name: Core
@@ -135,7 +137,7 @@ initializr:
bom: foo-bom
repository: foo-repo
versionRange: "[1.2.0.RELEASE,1.3.0.M1)"
```
----
If one selects this entry, the `com.example.foo:foo-core}` dependency will be added
and the Bill of Materials and repository for `foo` will be added automatically to
@@ -166,7 +168,8 @@ support is meant to react to that.
For instance, if you want your groupId to default to `org.acme` and the
`javaVersions` to only be `1.8` and `11` you would write the following config:
```yml
[source,yaml,indent=0]
----
initializr:
groupId:
value: org.acme
@@ -175,4 +178,4 @@ initializr:
default: false
- id: 1.8
default: true
```
----