resolves#81
Using LockRegistryLeaderInitiator to do leadership election.
When task is started and singleInstanceEnabled isset to true then we use leader election
to determine if a task needs to be started.
Error Event Name had to be updated
* cleanup removing unused headers
* Updated asserts in code base that needed messages (marked as deprecated)
* left one test that was testing a deprecated constructor. When that code is removed we can remove that test.
* some other cleanup
resolves#338
Updated to remove all commons-logging-api dependencies to resolve logging issue.
Updated to handle 2.0.0.M3 Spring Cloud Stream
resovles #347
Changes based on code review
resolves#303
Added support for DB2ZOS DatabaseType.
Added DB2AS400, DB2VSE, based on how Spring Batch implemeted DB2 identification via metadata.
All DB2 database types will use the DB2 repository initialize sql script
Tested this against a local DB2.
This commit removes the dependency on any Spring Boot starters.
Starters are still used in the test scope, but should not impact the
library's dependencies.
Resolves#294
When using Spring Boot, the id of the application context can be a colon
delimited string of values. By default, Spring Cloud Task uses this
value as the task name. However, when using JMX, this can cause issues.
This commit updates the SimpleTaskNameResolver to clense the colons and
replace them with underscores.
Resolves#280
* Updated the migration scripts to use all caps for table names
In the original migration scripts the table names were all lower case. However the original table definitions were capitalized, and on file systems that are case sensitive,
mysql fails to update the table. Because of the 2 different cases.
resolves#287
* Updated the 1.1.x branch migration scripts
In the original migration scripts the table names were all lower case. However the original table definitions were capitalized, and on file systems that are case sensitive,
mysql fails to update the table. Because of the 2 different cases.
* Added migration script for db2.
This commit adds the TaskExecutionListenerSupport, a no-op
implementation of the TaskExecutionListner. This allows a user to extend
the TaskExecutionListenerSupport and simply override what they need
instead of implementing all of the methods.
resolves#115
* Fixes bug where if the user set the environment variable and commandline args a unique constraint would fire.
* Updated docs
* Removed deprecation
* Fixed version number for integration test.
Added integration tests for externally generated task executions
Add externalExecutionId
resolves#80
resolves#115
* Fixes bug where if the user set the environment variable and commandline args a unique constraint would fire.
* Updated docs
* Removed deprecation
* Fixed version number for integration test.
Added integration tests for externally generated task executions
* We had a discussion on this sometime back and it was decided at that time to keep these type of trims and verification in the Repository.
* Fixed bug where trimming was taking 1 character too many
* Updated ExitMessage maxSize test to verify size
* Added ErrorMessage maxSize Test
* While adding taskExplorer to the test noticed it was missing 2 basic tests and added those as well
To provide the ability to control task orchestration via the exit
message, we moved the stack trace storage to a new field. This means
that exit message is now a field we can use similar to how exit code is
in batch, and still have the stack trace of an unsuccessful task
execution stored.
Resolvesspring-cloud/spring-cloud-task#186
Disabled integration tests by default
Just some cleanup on merge
