- Make exit code nullable and only update of execution status can make it a valid integer
- Update JDBC create/start task execution queries to have exitCode as `null` values
- Update tests to validate/verify the appropirate exit code values for create/start/complete task executions
On merge had to add a pause to the TaskLauncherSinkTests to wait for the task to complete successfully Before we assumed that 0 was a satisfactory result meaning it was either running or completed. Now with the null being returned it could be zero or null. So we have to wait for the task to complete.
All version changes are present.
Fixed all Java-Doc Errors and warnings
* Due to the stricter nature of the javadoc compiler we can't wrap <ul> / <ui> in <p>
* We will also need to Push up a test app for taklauncher to work with. The old one fails to start now. Or use one of the task starters possibly.
* Built on the work from TASK-439C. Wait for that merge before merging this one.
* Replaced applicationFailedEvent class attribute with applicaitonFailedException
* Also polished the app used by the taskLauncherSink integration test
Migrating to use ApplicationContextRunner or ImportAutoConfiguration with SpringApp.run, instead of SpringApplicationBuilder, because builder does not handle AutoConfiguration properly
SimpleTaskAutoConfiguration now has an annotation AutoConfigureBefore the BatchTaskAutoConfig so that it is processed prior. THis is so that that BatchTaskAutoConfig can create the appropriate beans
SimpleTaskAutoConfiguration has new annotations so that it is AutoConfigured after BindingServiceConfiguration and after SimpleTaskAutoConfiguration. This is so that it does not attempt to start emitting messages before stream is ready and it can create the appropriate beans after SimpleTaskAutoConfiguration has run.
Renamed SimpleTaskConfiguration to SimpleTaskAutoConfiguration.
Task version updated to 2.1.0
Added missing headers
Updated documentation.
Deprecated EnableTask
Added ability to disable Task autoconfiguration.
Removed @EnableTask from tests
Resolves#439Resolves#440Resolves#448Resolves#466
- Add the ability to retrieve the last TaskExecution to:
- MapTaskExecutionDao
- JdbcTaskExecutionDao
- Refactor `JdbcTaskExecutionDao` and use `NamedParameterJdbcTemplate` for all persistence store calls
- Add the following TaskExecution methods to TaskExplorer:
- getLatestTaskExecutionsByTaskNames
- getLatestTaskExecutionForTaskName
- Add Tests
- Ensure that code is JDK7 compatible due to backporting needs
- Ensure commit backports to 1.2.x
Polishing on tests during merge
If a user adds spring-cloud-starter-config to the dependencies it has to add a proxy for the datasource else the Hikari connection pool pukes.
resolves#407
This PR adds a sample that illustrates the use of multiple DataSources
in a single Spring Cloud Task application.
Resolves#413
Updated based on code review
I corrected spelling and grammar and gave it a voice (flat, corporate) consistent with our other docs. I added a couple TODOs where I thought another sample would help.
Incorporated Glenn Renfro's comments
Glenn gave my work a thorough review (thanks, Glenn!). This commit incorporates his changes.
One more change
I missed one of Glenn's fixes (by forgetting to save one last time before the previous commit). I have corrected that oversight
This commit adds the ability to configure the order for the
TaskJobLauncherCommandLineRunner. It also provides minor polish on a
few other code review related items.
