Spring/spring-boot
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Polish

Browse Source 
Closes gh-4572
This commit is contained in:
Johnny Lim
2015-11-21 12:12:05 +09:00
committed by Stephane Nicoll
parent 31d7ebc96e
commit 8ec00c35bf
40 changed files with 70 additions and 70 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
spring-boot-docs/src/main/asciidoc/deployment.adoc
View File

@@ -572,7 +572,7 @@ Spring Boot application can be started as Windows service using
https://github.com/kohsuke/winsw[`winsw`].
A sample https://github.com/snicoll-scratches/spring-boot-daemon[maintained separately]
to the core of Spring Boot describes steps by steps how you can create a Windows service for
to the core of Spring Boot describes step by step how you can create a Windows service for
your Spring Boot application.

2
spring-boot-docs/src/main/asciidoc/spring-boot-features.adoc
View File

@@ -3964,7 +3964,7 @@ when searching for beans.
TIP: You need to be very careful about the order that bean definitions are added as these
conditions are evaluated based on what has been processed so far. For this reason,
we recommend only using `@ConditionalOnBean` and `@ConditionalOnMissingBean` annotations
we recommend only using `@ConditionalOnBean` and `@ConditionalOnMissingBean` annotations
on auto-configuration classes (since these are guaranteed to load after any user-define
beans definitions have been added).

6
spring-boot-docs/src/main/asciidoc/using-spring-boot.adoc
View File

@@ -913,7 +913,7 @@ dependencies out-of-the-box so you may want to have a look to the
{propdeps-plugin}[`propdeps-plugin`] in the meantime.
TIP: If you want to ensure that devtools is never included in a production build, you can
use set the `excludeDevtools` build property to completely remove the JAR. The property is
use the `excludeDevtools` build property to completely remove the JAR. The property is
supported with both the Maven and Gradle plugins.
@@ -1058,7 +1058,7 @@ in the same way.
==== Customizing the restart classloader
As described in the <<using-spring-boot-restart-vs-reload>> section above, restart
functionality is implemented by using two classloaders. For most applications this
approach works well, however, sometimes in can cause classloading issues.
approach works well, however, sometimes it can cause classloading issues.
By default, any open project in your IDE will be loaded using the "`restart`" classloader,
and any regular `.jar` file will be loaded using the "`base`" classloader. If you work on
@@ -1067,7 +1067,7 @@ customize things. To do this you can create a `META-INF/spring-devtools.properti
The `spring-devtools.properties` file can contain `restart.exclude.` and
`restart.include.` prefixed properties. The `include` elements are items that should be
pulled-up into the "`restart`" classloader, and the `exclude` elements are items that
pulled up into the "`restart`" classloader, and the `exclude` elements are items that
should be pushed down into the "`base`" classloader. The value of the property is a regex
pattern that will be applied to the classpath.