root
/
spring-boot
mirror of https://github.com/spring-projects/spring-boot.git
1
0
Fork 0
Code Issues Actions 9 Packages Projects Releases Wiki Activity

Polish 

Closes gh-16193
This commit is contained in:
Johnny Lim 2019-03-11 21:27:22 +09:00 committed by Stephane Nicoll
parent 8a0dc61c59
commit bcfbabe6cd
4 changed files with 3 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -2626,7 +2626,7 @@ There are several options for hot reloading. The recommended approach is to use
additional development-time features, such as support for fast application restarts additional development-time features, such as support for fast application restarts
and LiveReload as well as sensible development-time configuration (such as template and LiveReload as well as sensible development-time configuration (such as template
caching). Devtools works by monitoring the classpath for changes. This means that static caching). Devtools works by monitoring the classpath for changes. This means that static
resource changes must be "built" for the change to take affect. By default, this happens resource changes must be "built" for the change to take effect. By default, this happens
automatically in Eclipse when you save your changes. In IntelliJ IDEA, the Make Project automatically in Eclipse when you save your changes. In IntelliJ IDEA, the Make Project
command triggers the necessary build. Due to the command triggers the necessary build. Due to the
<<using-spring-boot.adoc#using-boot-devtools-restart-exclude, default restart <<using-spring-boot.adoc#using-boot-devtools-restart-exclude, default restart

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

@ -8632,7 +8632,7 @@ documentation] for more details. You also need to
{junit5-documentation}/#writing-tests-test-instance-lifecycle-changing-default[switch test {junit5-documentation}/#writing-tests-test-instance-lifecycle-changing-default[switch test
instance lifecycle to "per-class"]. instance lifecycle to "per-class"].
To mock Kotlin classes, https://mockk.io/[Mockk] is recommended. If you need the `Mockk` To mock Kotlin classes, https://mockk.io/[MockK] is recommended. If you need the `Mockk`
equivalent of the Mockito specific equivalent of the Mockito specific
<<boot-features-testing-spring-boot-applications-mocking-beans,`@MockBean` and `@SpyBean` <<boot-features-testing-spring-boot-applications-mocking-beans,`@MockBean` and `@SpyBean`
annotations>>, you can use https://github.com/Ninja-Squad/springmockk[SpringMockK] which annotations>>, you can use https://github.com/Ninja-Squad/springmockk[SpringMockK] which

1
spring-boot-project/spring-boot/src/test/java/org/springframework/boot/diagnostics/analyzer/NoSuchMethodFailureAnalyzerTests.java
View File

@ -44,7 +44,6 @@ public class NoSuchMethodFailureAnalyzerTests {
assertThat(failure).isNotNull(); assertThat(failure).isNotNull();
FailureAnalysis analysis = new NoSuchMethodFailureAnalyzer().analyze(failure); FailureAnalysis analysis = new NoSuchMethodFailureAnalyzer().analyze(failure);
assertThat(analysis).isNotNull(); assertThat(analysis).isNotNull();
System.out.println(analysis.getDescription());
assertThat(analysis.getDescription()) assertThat(analysis.getDescription())
.contains(NoSuchMethodFailureAnalyzerTests.class.getName() .contains(NoSuchMethodFailureAnalyzerTests.class.getName()
+ ".createFailure(") + ".createFailure(")

2
spring-boot-tests/spring-boot-integration-tests/spring-boot-launch-script-tests/README.adoc
View File

@ -31,7 +31,7 @@ Next, add your user to the `docker` group. For example:
$ sudo usermod -a -G docker awilkinson $ sudo usermod -a -G docker awilkinson
---- ----
You may need to log out and back in again for this change to take affect and for your You may need to log out and back in again for this change to take effect and for your
user to be able to connect to the daemon. user to be able to connect to the daemon.