This commit removes the warnings that Maven emits when building the
effective model of the project. This boils down to locking down plugin
versions.
Because there is no version for javaformat, Maven could decide to use
the latest, which requires extra care to build with Java 8. This commit
upgrades explicitly to the latest and configure it to be compatible
with Java 8
* Do not apply javaformat by default
This commit removes the invocation of spring-javaformat:apply by
default. Doing so makes the validate goal irrelevant as apply is
going to reformat the code if necessary.
The idea of the plugin is that it should prevent you from pushing
something that has formatting violations. Running the build, run the
apply goal manually, and amending the commit is the idiomatic way of
using this plugin.
* Apply formatting
- remove unnecessary template delimiters from tests
- make expression handling consistent
- template delimiters should not be needed for any
- fix bean resolution in `@BackOff`
Fixes: https://github.com/spring-projects/spring-retry/issues/256
This suppresses the info message "Bean 'org.springframework.retry.annotation.RetryConfiguration' of type [org.springframework.retry.annotation.RetryConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)" during the Spring context start.
* Avoid static import, fix copyright year, add author
Resolves https://github.com/spring-projects/spring-retry/issues/244
The `RecoverAnnotationRecoveryHandler` only has access to the undecorated
raw bean.
Use the `RetryContext` to make the proxy (if CGLIB) available to the recoverer.
* Move cleanup to a finally block.
* Support JDK proxies too.
* Add CGLib proxy test; JDK proxies are covered by existing tests.
Resolves https://github.com/spring-projects/spring-retry/issues/237
- also don't include non-singletons or perform eager inits
- `spring-javaformat` has reformatted some other code
* Update main branch name in README.
* Fix `getBeansOfType()`.
Fixes https://github.com/spring-projects/spring-retry/issues/234
Currently `UniformRandomBackOffPolicy` loses `maxBackOffPeriod` when `withSleeper` is used
* Propagate `maxBackOffPeriod` into a new `UniformRandomBackOffPolicy` instance produced
by the `withSleeper(Sleeper)` API
It isn't really optional, but no-one uses Spring Retry without it
and some older build systems (Gradle old versions) don't like finding
multiple versions of thw same library.
