Spring Cloud Task 2.1.0 GA is now available

We are pleased to announce that Spring Cloud Task 2.1.0.RELEASE is now available on Github and the Pivotal download repository. Many thanks to all of those who contributed to this release.

What’s New?

Spring Cloud Task 2.1.0.RELEASE is intended to be the version of the framework aligned with Spring Boot 2.1.0. Updates from 2.1.x include:

  • Update all dependencies.
  • Spring Cloud Task infrastructure components are now enabled through auto-configuration.
  • The exitCode of a TaskExecution is null when a task is executing.
  • Spring Cloud Task is compatible with Java 8, 9, 10, 11.

Let’s walk through these updates in more detail.

Update to All Dependencies

As stated earlier, this release brings Spring Cloud Task into alignment with Spring Boot 2.1. This includes updating all dependencies.

Spring Cloud Task Foundation Components are Now Enabled through Auto-configuration

Auto configuration is now used to create the TaskExplorer, TaskRepository, and other beans but does not create the TaskLifecycleListener (the bean that executes the Spring Cloud Task core functionality). We added this feature to let users who are building their own applications that are not tasks monitor or browse the task repository by using the provided auto configuration. The TaskLifecycleListener bean is created when a user adds the @EnableTask to their application or configuration.

Task Execution’s exitCode Is Null When a Task Executes

In previous releases of Spring Cloud Task, the TaskExecution returned from Spring Cloud Task always showed that a running task’s exitCode was 0. Now the TaskExecution instances returned from Spring Cloud Task have an exitCode of null if the task is still executing.

What Do You Think?

We look forward to your feedback on these new features in Github, on StackOverflow, Gitter, or directly via Twitter to @michaelminella or @cppwfs!

Spring Cloud Task Home | Source on GitHub | Reference Documentation

comments powered by Disqus