You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Removed Failsafe.with(Policy[])
- Removed volatile from event listener members. This can be added in the future if these ever become mutable after a policy is built.
Copy file name to clipboardExpand all lines: CHANGELOG.md
+4-2
Original file line number
Diff line number
Diff line change
@@ -8,10 +8,11 @@ This release introduces breaking changes to the API:
8
8
#### General
9
9
10
10
- All files have been moved to the `dev.failsafe` package. Be sure to update your imports.
11
+
-`Failsafe.with(P[] policies)` was removed.
11
12
12
13
#### Policies
13
14
14
-
- All policies are now threadsafe and use a builder API. The configuration methods available in the builder are mostly the same as previously with the 2.x policies. Some notes:
15
+
- All policies now use a builder API. The configuration methods available in the builder are mostly the same as previously with the 2.x policies. Some notes:
15
16
- A policy builder can be created via `builder()`.
16
17
-`RetryPolicy` and `CircuitBreaker` can be constructed with default values using `ofDefaults()`.
17
18
- Policy configuration is accessible via a `getConfig()`.
@@ -57,11 +58,12 @@ The following changes effect the SPI classes, for users who are extending Failsa
57
58
58
59
### Improvements
59
60
61
+
- Issue #47 - All policies and policy config classes are now threadsafe. Policy builders are not threadsafe.
62
+
- Issue #201 - Thread safety is clearly documented in policy, policy config, and policy builder classes.
60
63
- Issue #292 - Created an extensible Policy SPI.
61
64
- Issue #254 - Added an explicit `compose` method to `FailsafeExecutor`.
62
65
- Issue #293 - Added `RetryPolicyBuilder.withBackoff(Duration, Duration)` and `.withDelay(Duration, Duration)`.
63
66
- Issue #221 - `Executor` instances configured via `FailsafeExecutor.with(Executor)` are now used on all executions, including sync executions, and can be used in conjunction with a separately configured `ExecutorService` or `Scheduler` for async executions.
64
-
- Issue #47 - Thread safety is now clearly documented in the policy, policy builder, and policy config classes. Policy and policy config classes are threadsafe. Policy builder classes are not threadsafe.
0 commit comments