Phillip Webb
Phillip Webb
Currently our tools API docs are mixed with our regular API docs. ``` .findAll { !it.path.contains(":spring-boot-tools:") || it.path.contains(":spring-boot-tools:spring-boot-buildpack-platform") || it.path.contains(":spring-boot-tools:spring-boot-loader-tools") } ``` It might be better to have a `/tools/api/java`...
The [webinar](https://tanzu.vmware.com/content/webinars/apr-16-spring-on-kubernetes) presented by @ryanjbaxter has an interesting bit of configuration to delay shutdown using a `preStop` command. [This article](https://blog.gruntwork.io/delaying-shutdown-to-wait-for-pod-deletion-propagation-445f779a8304) has some interesting background. We might be able to offer...
Any existing links to `https://docs.spring.io/spring-boot/docs/current/reference/htmlsingle/#` or `https://docs.spring.io/spring-boot/docs/current/reference/html/#` will break since we've migrated to Antora. Additionally our anchor rewrite rules will also fail. We ideally need a strategy to help users...
There's a lot of copy/paste at the moment, especially with the tabs markup. We could use something like `code-include` if it could be configured differently.
We currently link to source code for configuration properties info. E.g ```asciidoc For more detail, see the {spring-boot-actuator-autoconfigure-module-code}/web/server/ManagementServerProperties.java[`ManagementServerProperties`] source code and "`xref:ROOT:actuator/monitoring.adoc#actuator.monitoring.customizing-management-server-port[Customizing the Management Server Port]`" in the "`Production-ready features`"...
Currently we [never set a description for item groups](https://github.com/spring-projects/spring-boot/blob/d0421fa2d64f506c362199901929d858d916a5c6/spring-boot-project/spring-boot-tools/spring-boot-configuration-processor/src/main/java/org/springframework/boot/configurationprocessor/PropertyDescriptor.java#L175), however, our documentation does say that one can be provided in the JSON. It would be nice if we could find...
See #40206 for one example of the problem direct binding currently causes. We'd like to have a package-private `ApplicationProperties` that we bind to then use `PropertyMapper` (or something similar).
It would be nice if we could improve the way we link to both external and internal classes. We could probably write an extension that would support the form: ```...
``` > Task :spring-boot-project:spring-boot-devtools:checkArchitectureTest > Task :spring-boot-project:spring-boot-devtools:checkCompileClasspathForProhibitedDependen***es > Task :spring-boot-project:spring-boot-devtools:checkIntTestCompileClasspathForProhibitedDependen***es > Task :spring-boot-project:spring-boot-devtools:checkIntTestRuntimeClasspathForProhibitedDependen***es > Task :spring-boot-project:spring-boot-devtools:checkRuntimeClasspathForProhibitedDependen***es > Task :spring-boot-project:spring-boot-devtools:checkSpringConfigurationMetadata > Task :spring-boot-project:spring-boot-devtools:checkTestCompileClasspathForProhibitedDependen***es > Task :spring-boot-project:spring-boot-devtools:checkTestRuntimeClasspathForProhibitedDependen***es ```
It looks like an asciidoctor import is failing for the [Appendix](https://docs.spring.io/spring-data/geode/docs/2.3.x/reference/html/#appendix-schema) since 2.3. The following message is in the docs: ``` Appendices Unresolved directive in index.adoc - include::../../../../spring-data-commons/src/main/asciidoc/repository-namespace-reference.adoc[leveloffset=+1] Unresolved directive...