All Versions
53
Latest Version
Avg Release Cycle
87 days
Latest Release
-

Changelog History
Page 5

  • v0.8.3 Changes

    🐛 Bug Fixes

    • 🛠 Fixed #33 - CircuitBreaker not decrementing currentExections when under load

  • v0.8.2 Changes

    🆕 New Features

    • ➕ Added support for onRetriesExceeded listeners.
    • RetryPolicy can be extended (it's no longer marked as final)

    🐛 Bug Fixes

    • Abort should not call failure listeners.

  • v0.8.1 Changes

    🆕 New Features

    • Simplified listeners API.
    • ➕ Added support for failure listeners via Failsafe.with(...).onFailure(e -> {}).
    • ➕ Added onAbort listeners.
    • ➕ Added additional async listeners.
    • 🔧 RetryPolicy and CircuitBreaker now support multiple configuration rules. Ex: new RetryPolicy().retryWhen(null).retryWhen(""). If any rule matches then the policy is matched.

    API Changes

    • ➕ Added top level support for listener registration via Failsafe.with(...).onXxx. The Listeners class is now only meant for Java 6 and 7 usage via method overrides.
    • ✂ Removed listener registration from Listeners class.
    • ✂ Removed AsyncListeners class.
    • ✂ Removed listener registration from FailsafeFuture class.

  • v0.8.0 Changes

    🆕 New Features

    • ➕ Added support for circuit breakers

    API Changes

    • Project renamed from Recurrent to Failsafe

  • v0.7.1 Changes

    🐛 Bug Fixes

    • ➕ Added better support for scheduling failure handling
    • 🛠 Fixed RetryPolicy failure assignability checking

    API Changes

    • 👍 Invocation APIs were renamed to Execution to better align with the java.util.concurrent naming.
    • InvocationStats.getAttemptCount() was renamed to ExecutionStats.getExecutions()

  • v0.7.0 Changes

    🆕 New Features

    • ➕ Added additional contextual callable and runnable support

    API Changes

    • 🔄 Changed to a new API entry point: Recurrent.with.
    • ➕ Added .with for configuring listeners.

  • v0.6.0 Changes

    🆕 New Features

    • ➕ Added RetryPolicy.abortOn, abortWhen and abortIf methods to abort retries when matched.

    API Changes

    • RetryPolicy.retryWhen was renamed to retryIf for retrying if a Predicate is matched.
    • RetryPolicy.retryFor was renamed to retryWhen for retrying when a result is matched.
    • ⏱ Scheduler and Schedulers were moved to net.jodah.recurrent.util.concurrent.

  • v0.5.0 Changes

    🆕 New Features

    • ➕ Added support for synchronous and asynchronous event listeners
    • ➕ Added support for CheckedRunnable

    API Changes

    • The Recurrent.run methods now require a CheckedRunnable rather than Runnable. This allows Recurrent to be used on code that throws checked exceptions without having to wrap the code in try/catch blocks.
    • 🔀 The synchronous Recurrent.run and Recurrent.get methods will throw a RecurrentException if a failure occurs and the retry policy is exceeded.

  • v0.4.0 Changes

    🆕 New Features

    • ➕ Added better support for invocation tracking

    API Changes

    • 🆕 New Invocation and AsyncInvocation APIs

  • v0.3.3 Changes

    🆕 New Features

    • ➕ Add Scheduler API
    • 👉 Make RetryPolicy copyable

    Behavior Changes

    • Require ContextualCallable and ContextualRunnable to be manually retried
    • ➕ Add support for checking multiple retry policy conditions

    API Changes

    • 👻 Make ContextualRunnable throw Exception