@@ -3128,9 +3128,9 @@ include::{testDir}/example/TempDirectoryDemo.java[tags=user_guide_field_injectio
3128
3128
----
3129
3129
3130
3130
The `@TempDir` annotation has an optional `cleanup` attribute that can be set to either
3131
- `NEVER`, `ON_SUCCESS`, or `ALWAYS`. If the cleanup mode is set to `NEVER`, temporary
3132
- directories are not deleted after a test completes. If it is set to `ON_SUCCESS`,
3133
- temporary directories are deleted only after a test completed successfully.
3131
+ `NEVER`, `ON_SUCCESS`, or `ALWAYS`. If the cleanup mode is set to `NEVER`, the temporary
3132
+ directory will not be deleted after the test completes. If it is set to `ON_SUCCESS`, the
3133
+ temporary directory will only be deleted after the test if the test completed successfully.
3134
3134
3135
3135
The default cleanup mode is `ALWAYS`. You can use the
3136
3136
`junit.jupiter.tempdir.cleanup.mode.default`
@@ -3166,7 +3166,7 @@ prefix instead of the `junit` constant value.
3166
3166
include::{testDir}/example/TempDirectoryDemo.java[tags=user_guide_factory_name_prefix]
3167
3167
----
3168
3168
3169
- It's also possible to use an in-memory file system like `{Jimfs}` for the creation of the
3169
+ It is also possible to use an in-memory file system like `{Jimfs}` for the creation of the
3170
3170
temporary directory. The following example demonstrates how to achieve that.
3171
3171
3172
3172
[source,java,indent=0]
@@ -3197,18 +3197,17 @@ include::{testDir}/example/TempDirectoryDemo.java[tags=user_guide_composed_annot
3197
3197
Meta-annotations or additional annotations on the field or parameter the `TempDir`
3198
3198
annotation is declared on might expose additional attributes to configure the factory.
3199
3199
Such annotations and related attributes can be accessed via the `AnnotatedElementContext`
3200
- parameter of `createTempDirectory` .
3200
+ parameter of the `createTempDirectory(...)` method .
3201
3201
3202
- You can use the `junit.jupiter.tempdir.factory.default`
3203
- <<running-tests-config-params, configuration parameter>> to specify the fully qualified
3204
- class name of the `TempDirFactory` you would like to use by default. Just like for
3205
- factories configured via the `factory` attribute of the `@TempDir` annotation,
3206
- the supplied class has to implement the `TempDirFactory` interface. The default factory
3207
- will be used for all `@TempDir` annotations unless the `factory` attribute of the
3208
- annotation specifies a different factory.
3202
+ You can use the `junit.jupiter.tempdir.factory.default` <<running-tests-config-params,
3203
+ configuration parameter>> to specify the fully qualified class name of the
3204
+ `TempDirFactory` you would like to use by default. Just like for factories configured via
3205
+ the `factory` attribute of the `@TempDir` annotation, the supplied class has to implement
3206
+ the `TempDirFactory` interface. The default factory will be used for all `@TempDir`
3207
+ annotations unless the `factory` attribute of the annotation specifies a different factory.
3209
3208
3210
- In summary, the factory for a temporary directory is determined according to the
3211
- following precedence rules:
3209
+ In summary, the factory for a temporary directory is determined according to the following
3210
+ precedence rules:
3212
3211
3213
3212
1. The `factory` attribute of the `@TempDir` annotation, if present
3214
3213
2. The default `TempDirFactory` configured via the configuration
0 commit comments