Glenn Renfro
Glenn Renfro
The following methods are to be removed: * getComposedTaskRunnerUri * setComposedTaskRunnerUri * isUseUserAccessToken * setUseUserAccessToken And the instances where they are used the code should use the properties in `composedTaskRunnerConfigurationProperties`.
Currently SimpleJobService sets the JobExecution to `Stopping` or `Stopped`. This signals that the batch job to stop on the next step, which is normal. However, it does not support stopping...
TaskExplorer side of issue resolved in Spring Cloud Task 3.2-M1 JdbcSearchableJobExecutionDao.createJobExecutionFromResultSet is currently failing on this issue.
Spring Batch 5.2.x supports MongoDB for its Job Schema. Task needs to provide support Job and Task database entries that are stored in MongoDB.
SCDF provides cron expression for scheduling the launching of tasks. However, users sometimes need more advanced scheduling for launching their tasks. In these cases they can use enterprise level schedulers...
Update SCDF's usage of the following Deprecated warnings based on the recommendation actions: - [x] `asList()` is deprecated - [x] StreamControllerTests - [x] `configure(com.fasterxml.jackson.databind.MapperFeature, boolean)` is deprecated - [x] CloudFoundryApplicationManifestReader...
This includes replacing the apis utilized from this dependency to the ones provided by cloudfoundry-reactve-client. For example the scheduling calls made in the class `CloudFoundrySchedulerClientProvider`.
Based on the following comment: https://github.com/spring-cloud/spring-cloud-task/issues/769#issuecomment-2513846920, a transaction manager is still being created eventhough the spring.cloud.task.transaction-manager is being used. Investigate.
This includes replacing the apis utilized from this dependency to the ones provided by cloudfoundry-reactve-client. For example the scheduling calls made in the class CloudFoundrySchedulerClientProvider.