spring-cloud-task

Files

Spring Operator 505fd21ff9 URL Cleanup

This commit updates URLs to prefer the https protocol. Redirects are not followed to avoid accidentally expanding intentionally shortened URLs (i.e. if using a URL shortener).

# HTTP URLs that Could Not Be Fixed
These URLs were unable to be fixed. Please review them to see if they can be manually resolved.

* http://xslthl.sf.net (301) with 1 occurrences could not be migrated:
   ([https](https://xslthl.sf.net) result AnnotatedConnectException).

# Fixed URLs

## Fixed Success
These URLs were switched to an https URL with a 2xx status. While the status was successful, your review is still recommended.

* http://asciidoctor.org with 1 occurrences migrated to:
  https://asciidoctor.org ([https](https://asciidoctor.org) result 200).
* http://maven.apache.org/xsd/maven-4.0.0.xsd with 18 occurrences migrated to:
  https://maven.apache.org/xsd/maven-4.0.0.xsd ([https](https://maven.apache.org/xsd/maven-4.0.0.xsd) result 200).
* http://sourceforge.net/projects/xslthl/ with 14 occurrences migrated to:
  https://sourceforge.net/projects/xslthl/ ([https](https://sourceforge.net/projects/xslthl/) result 200).
* http://www.w3.org/TR/CSS21/propidx.html with 1 occurrences migrated to:
  https://www.w3.org/TR/CSS21/propidx.html ([https](https://www.w3.org/TR/CSS21/propidx.html) result 200).

# Ignored
These URLs were intentionally ignored.

* http://maven.apache.org/POM/4.0.0 with 36 occurrences
* http://www.w3.org/2001/XMLSchema-instance with 18 occurrences

2019-03-19 21:26:51 -05:00

.mvn/wrapper

SCT-12 Creates the SCSt sink that can launch tasks.

2016-03-23 11:11:24 -05:00

src

Cleanup from Checkstyle changes

2019-02-13 12:21:14 -05:00

mvnw

URL Cleanup

2019-03-11 12:48:37 -05:00

mvnw.cmd

URL Cleanup

2019-03-11 12:48:37 -05:00

pom.xml

URL Cleanup

2019-03-19 21:26:51 -05:00

README.adoc

Refactored the use of the name parameters to be arguments

2016-06-09 09:39:14 -05:00

README.adoc

= TaskProcessor

Is a stream processor that will accept messages with a string payload and create a
`TaskLaunchRequest` that it will send to the next app in the stream. The payload of the
message that is sent will be added to the properties of the `TaskLaunchRequest` under
the `payload` key.

By default the processor will add the timestamp-task sample coordinates if no task is
specified.

NOTE: if using defaults make sure to install the timestamp-task into your local maven repo
by executing the following build in the timestamp-task module:

[source,shell,indent=2]
----
$ ./mvnw clean install
----

== The arguments offered by the TaskProcessor are as follows:
* *group* establishes the group for the task maven coordinates. Default is `io.spring`.
* *artifact* establishes the artifact for the task maven coordinates. Default is `timestamp-task`.
* *classifiers* establishes the classifier for the task maven coordinates. Default is null.
* *extension* establishes the extension for the task maven coordinates. Default is jar.
* *data-source-url* sets the spring_datasource_url for the task. Default is null.
* *data-source-driver-class-name* establishes the spring_datasource_driverClassName for the task. Default is null.
* *data-source-user-name* establishes the spring_datasource_username for the task. Default is null.
* *data-source-password* establishes the spring_datasource_password for the task. Default is null.

== Requirements:

* Java 7 or Above

== Build:

[source,shell,indent=2]
----
$ ./mvnw clean install
----

== Dependencies:

The task processor requires an instance of RabbitMQ to be running.