Artem Bilan

We cannot guess that because even simple `` for the mentioned `TimeoutRetryPolicy` would fail if we had setters like `setTimeout(long)` and `setTimeout(Duration)`. It would be a bit awkward to have...

Yeah... So, let's start then from the `RetryTemplateBuilder` introducing new methods based on a `Duration` even if internally we still have to convert it back to the `toMillis()` to satisfy...

Thank you for the pointer, @quaff . Unfortunately we cannot upgrade there yet. For that we would need a new version to start for this project. We have some plans...

@samirm , any chances you can share with us a code which may reproduce the issue? The simple Spring Boot project to play with would be great. Thanks

Well, according to the issue description this is not the case. Looks like those `@Retryable` and `@Scheduled` are in different classes. Therefore there is no AOP advices ordering issue since...

The JavaDoc stays right now that it is not a "no backoff": ``` /** * Specify the backoff properties for retrying this operation. The default is a simple * {@link...

Spring Retry does not have transitive dependencies at all. Everything is optional and in most cases compatible with wide range of Spring versions. So, it is indeed expected that you...

@dturanski , would you mind answering or at least helpping who can? The Splunk `Job` has states: `isDone()`, `isFailed()`, `isFinalized()`, `isPaused()`. How are they related to each other? The `Job`...

Pushed the implementation for `realtime search`. Pay attention, please, to the `SplunkDataReader#isJobInvalid()` method. Testing with real Splunk Enterprise shows that `finalized` and `failed` states impact to the `done` one and...

Since RT search Job is long-living but we can `start/stop` adapter at runtime, consider to `finish()` Splunk Job on adapter `stop()`. See https://jira.spring.io/browse/INT-3571