Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Sign in / Register
Toggle navigation
S
spring-boot
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
DEMO
spring-boot
Commits
012a9564
Commit
012a9564
authored
Feb 15, 2019
by
Madhura Bhave
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Fix typo in doc
parent
33b93210
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
2 deletions
+2
-2
usage.apt.vm
...-tools/spring-boot-maven-plugin/src/site/apt/usage.apt.vm
+2
-2
No files found.
spring-boot-project/spring-boot-tools/spring-boot-maven-plugin/src/site/apt/usage.apt.vm
View file @
012a9564
...
@@ -62,7 +62,7 @@ Usage
...
@@ -62,7 +62,7 @@ Usage
Devtools is automatically excluded by default (you can control that using the
Devtools is automatically excluded by default (you can control that using the
<<<excludeDevtools>>> property). In order to make that work with <<<war>>> packaging,
<<<excludeDevtools>>> property). In order to make that work with <<<war>>> packaging,
the
`spring-boot-devtools`
dependency must be set as <<<optional>>> or with the
the
<<<spring-boot-devtools>>>
dependency must be set as <<<optional>>> or with the
<<<provided>>> scope.
<<<provided>>> scope.
The original (i.e. non executable) artifact is renamed to <<<.original>>> by default but it is also
The original (i.e. non executable) artifact is renamed to <<<.original>>> by default but it is also
...
@@ -219,7 +219,7 @@ spring.devtools.remote.restart.enabled=false
...
@@ -219,7 +219,7 @@ spring.devtools.remote.restart.enabled=false
* Working with integration tests
* Working with integration tests
While you may start your Spring Boot application very easily from your test (or test suite) itself,
While you may start your Spring Boot application very easily from your test (or test suite) itself,
it may be desirable to handle that in the build itself. To make sure that the lifecycle of you Spring
it may be desirable to handle that in the build itself. To make sure that the lifecycle of you
r
Spring
Boot application is properly managed <around> your integration tests, you can use the <<<start>>> and
Boot application is properly managed <around> your integration tests, you can use the <<<start>>> and
<<<stop>>> goals as described below:
<<<stop>>> goals as described below:
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment