|
Build and Deploy Snapshot / Build and Deploy Snapshot (push) Waiting to run
Details
Build and Deploy Snapshot / Trigger Docs Build (push) Blocked by required conditions
Details
Build and Deploy Snapshot / Verify (push) Blocked by required conditions
Details
CI / ${{ matrix.os.name}} | Java ${{ matrix.java.version}} (map[toolchain:false version:25], map[id:${{ vars.UBUNTU_MEDIUM || 'ubuntu-latest' }} name:Linux]) (push) Waiting to run
Details
CI / ${{ matrix.os.name}} | Java ${{ matrix.java.version}} (map[toolchain:false version:25], map[id:windows-latest name:Windows]) (push) Waiting to run
Details
CI / ${{ matrix.os.name}} | Java ${{ matrix.java.version}} (map[toolchain:true version:17], map[id:${{ vars.UBUNTU_MEDIUM || 'ubuntu-latest' }} name:Linux]) (push) Waiting to run
Details
CI / ${{ matrix.os.name}} | Java ${{ matrix.java.version}} (map[toolchain:true version:17], map[id:windows-latest name:Windows]) (push) Waiting to run
Details
CI / ${{ matrix.os.name}} | Java ${{ matrix.java.version}} (map[toolchain:true version:21], map[id:${{ vars.UBUNTU_MEDIUM || 'ubuntu-latest' }} name:Linux]) (push) Waiting to run
Details
CI / ${{ matrix.os.name}} | Java ${{ matrix.java.version}} (map[toolchain:true version:21], map[id:windows-latest name:Windows]) (push) Waiting to run
Details
Run CodeQL Analysis / run-analysis (push) Waiting to run
Details
Run System Tests / Java ${{ matrix.java.version}} (map[toolchain:true version:17]) (push) Waiting to run
Details
Run System Tests / Java ${{ matrix.java.version}} (map[toolchain:true version:21]) (push) Waiting to run
Details
Change `spring-boot-tomcat-runtime` and `spring-boot-jetty-runtime` into starter POMs and reduce the number of dependencies needed for `spring-boot-tomcat` and `spring-boot-jetty`. The runtime starters provide only the jars required to run the embedded server along with the module jar itself (excluding transitive dependencies) and `spring-boot-webserver` (excluding transitive dependencies). The build setup required for an executable jar is slightly different between Maven and Gradle. For Maven, the regular module is put in the `provided` scope. For Gradle, the regular module remains in main configuration and the runtime jar is put in the `providedRuntime` configuration. The reference documentation has been updated to show how to configure things if starters are being used. Manual testing has been performed to ensure that wars build with Maven and Gradle work with both Tomcat and Jetty in both deployed and `java -jar` modes. Closes gh-48175 |
||
|---|---|---|
| .. | ||
| spring-boot-dependencies | ||
| spring-boot-internal-dependencies | ||