- 12 Jan, 2021 28 commits
-
-
Andy Wilkinson authored
Fixes gh-24782
-
Stephane Nicoll authored
Closes gh-24765
-
Stephane Nicoll authored
-
Stephane Nicoll authored
Closes gh-24766
-
Stephane Nicoll authored
Closes gh-24781
-
Stephane Nicoll authored
Closes gh-24780
-
Stephane Nicoll authored
Closes gh-24779
-
Stephane Nicoll authored
Closes gh-24778
-
Stephane Nicoll authored
Closes gh-24777
-
Stephane Nicoll authored
Closes gh-24776
-
Stephane Nicoll authored
Closes gh-24775
-
Stephane Nicoll authored
Closes gh-24774
-
Stephane Nicoll authored
Closes gh-24773
-
Stephane Nicoll authored
Closes gh-24772
-
Stephane Nicoll authored
Closes gh-24771
-
Stephane Nicoll authored
Closes gh-24770
-
Andy Wilkinson authored
Fixes gh-24618
-
Stephane Nicoll authored
Closes gh-24764
-
Stephane Nicoll authored
Closes gh-24763
-
Stephane Nicoll authored
Closes gh-24762
-
Stephane Nicoll authored
Closes gh-24761
-
Stephane Nicoll authored
Closes gh-24760
-
Stephane Nicoll authored
Closes gh-24759
-
Stephane Nicoll authored
Closes gh-24758
-
Stephane Nicoll authored
Closes gh-24757
-
Stephane Nicoll authored
Closes gh-24756
-
Stephane Nicoll authored
Closes gh-24755
-
Stephane Nicoll authored
Closes gh-24754
-
- 11 Jan, 2021 4 commits
-
-
Phillip Webb authored
Closes gh-24747
-
Phillip Webb authored
Update `WebMvcAutoConfiguration` so that the default "/" resource path is registered directly as a `ServletContextResource`. Closes gh-24745
-
Andy Wilkinson authored
Previously, unlike the application plugin's run task, our bootRun task ignored the project's Java toolchain. This meant that the application was run on a JVM with the same Java version as the one being used by Gradle itself. This could result in a failure if the application required a more modern JVM. This commit updates the plugin to configure the bootRun task's JavaLauncher convention to be one derived from the project's Java toolchain. Toolchain support was introduced in Gradle 6.7 so this is only done when using Gradle 6.7 and later. Fixes gh-24517
-
Andy Wilkinson authored
Previously, bootRun assumed that the Java version of the JVM that would run the application would be the same as the Java version of the JVM that is running the build. This assumption does not hold true when Gradle's toolchain support is used to configure tasks that fork a new JVM to use a version other than that being used by Gradle itself. This commit updates the BootRun task to query the JavaLauncher property when determining the version of Java on which the application will be run. Toolchain support and the JavaLauncher property are new in Gradle 6.7. To support earlier versions of Gradle, NoSuchMethodError is caught we continue as if no JavaLauncher has been configured and use the local JVM's Java version. Fixes gh-24512
-
- 08 Jan, 2021 2 commits
-
-
Andy Wilkinson authored
This reverts commit ad164269 and adds some additional tests. Fixes gh-24192
-
Stephane Nicoll authored
Closes gh-24705
-
- 07 Jan, 2021 6 commits
-
-
Madhura Bhave authored
Closes gh-24677
-
Scott Frederick authored
This commit removes the `layout` and `layoutFactory` parameters from the `build-image` goal in the Maven plugin while retaining them for the `repackage` goal. The `build-image` goal currently only supports jar archives, so allowing other layout types to be configured for the goal could cause confusion. Fixes gh-24105
-
Phillip Webb authored
Update `FailureAnalyzers` to log errors at `trace` rather than `debug`. This should reduce noise when an analyzer unexpectedly fails and the user is running with `--debug`. Fixes gh-24630
-
Phillip Webb authored
-
Phillip Webb authored
Update formula to use spring-boot rather than springboot. This will allow both taps to be used at the same time. See gh-24659
-
Phillip Webb authored
Closes gh-24680
-