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

Restore monospaced text to unescaped form

Browse Source 
See gh-41614
This commit is contained in:
Phillip Webb
2024-11-20 20:35:33 -08:00
parent 4c8dafe12b
commit 6b6597b403
37 changed files with 91 additions and 91 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
spring-boot-project/spring-boot-docs/src/docs/antora/modules/specification/pages/configuration-metadata/format.adoc
View File

@@ -246,12 +246,12 @@ The JSON object contained in the `hints` array can contain the attributes shown
| `values`
| ValueHint[]
| A list of valid values as defined by the `+ValueHint+` object (described in the next table).
| A list of valid values as defined by the `ValueHint` object (described in the next table).
Each entry defines the value and may have a description.
| `providers`
| ValueProvider[]
| A list of providers as defined by the `+ValueProvider+` object (described later in this document).
| A list of providers as defined by the `ValueProvider` object (described later in this document).
Each entry defines the name of the provider and its parameters, if any.
|===

4
spring-boot-project/spring-boot-docs/src/docs/antora/modules/specification/pages/executable-jar/jarfile-class.adoc
View File

@@ -18,8 +18,8 @@ myapp.jar
0063 3452 3980
----
The preceding example shows how `+A.class+` can be found in `/BOOT-INF/classes` in `myapp.jar` at position `0063`.
`+B.class+` from the nested jar can actually be found in `myapp.jar` at position `3452`, and `+C.class+` is at position `3980`.
The preceding example shows how `A.class` can be found in `/BOOT-INF/classes` in `myapp.jar` at position `0063`.
`B.class` from the nested jar can actually be found in `myapp.jar` at position `3452`, and `C.class` is at position `3980`.
Armed with this information, we can load specific nested entries by seeking to the appropriate part of the outer jar.
We do not need to unpack the archive, and we do not need to read all entry data into memory.

2
spring-boot-project/spring-boot-docs/src/docs/antora/modules/specification/pages/executable-jar/property-launcher.adoc
View File

@@ -20,7 +20,7 @@ The following table describes these properties:
| Default arguments for the main method (space separated).
| `loader.main`
| Name of main class to launch (for example, `+com.app.Application+`).
| Name of main class to launch (for example, `com.app.Application`).
| `loader.config.name`
| Name of properties file (for example, `launcher`).

2
spring-boot-project/spring-boot-docs/src/docs/antora/modules/specification/pages/executable-jar/restrictions.adoc
View File

@@ -17,5 +17,5 @@ The content of the nested jar file itself can still be compressed, as can any ot
* System classLoader:
Launched applications should use `Thread.getContextClassLoader()` when loading classes (most libraries and frameworks do so by default).
Trying to load nested jar classes with `ClassLoader.getSystemClassLoader()` fails.
`+java.util.Logging+` always uses the system classloader.
`java.util.Logging` always uses the system classloader.
For this reason, you should consider a different logging implementation.