505fd21ff9
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
= Task Events This is a task application that emits batch job events to the following channels: * job-execution-events * step-execution-events * chunk-events * item-read-events * item-process-events * item-write-events * skip-events Note: More information on this topic is available https://docs.spring.io/spring-cloud-task/current-SNAPSHOT/reference/htmlsingle/#stream-integration-batch-events[here]. == Requirements: * Java 7 or Above == Build: [source,shell,indent=2] ---- $ ./mvnw clean install ---- == Execution: [source,shell,indent=2] ---- $ java -jar target/batch-events-1.2.1.RELEASE.jar ---- For example you can listen for specific job execution events on a specified channel with a Spring Cloud Stream Sink like the log sink using the following: [source,shell,indent=2] ---- $ java -jar <PATH_TO_LOG_SINK_JAR>/log-sink-rabbit-1.0.2.RELEASE.jar --server.port=9090 --spring.cloud.stream.bindings.input.destination=job-execution-events ---- == Dependencies: The batch-events sample requires an instance of RabbitMQ to be running.