BATCH-2247: Added creation of a JobExplorer by default to address the inability to create a Map based JobExplorer using java config
BATCH-2242: Stopping a job in STARTING state throws OptimisticLockingFailureException
BATCH-2250: Added @FixMethodOrder(MethodSorters.JVM) to override new default method sorting by JUnit 4.11
Temporarily ignore test until build issue is fixed
Remove @Ignore from test, fix build system issue
Re-ignore.. apparently not the appropriate fix..
Final attempt at fixing test failure on build machine. Works as expected in a cloned plan
BATCH-2251: Removed unused property from provided properties files
BATCH-2257: Added process skip count and filter count to the aggregate
BATCH-2253: Added automatic registraiton of Job Scope to java config and
added support for a @JobScope annotation.
XD-1027: Create script-based batch ItemProcessor
BATCH-2283: Updated MessageChannelPartitionHandler to return null when no partitions are specified
BATCH-2241 & BATCH-2243 - add namespace support for remote chunking
Add null check to AsyncItemWriter

The AsyncItemWriter is used in conjunction with the AsyncItemProcessor
to unwrap the Futures that are returned by that processor.
Traditionally when an ItemProcessor returns null, it's considered having
been filtered out and should not be passed to the ItemWriter.  In this
case, the AsyncItemWriter was not checking for nulls so they were being
passed to the delegate ItemWriter.  Most of the OOTB ItemWriters do not
perform a null check prior to doing the write so they were throwing NPEs
when using this paradigm.
BATCH-1863: The batch namespace can not be used with allowBeanDefinitionOverriding=false
Deleting an unnecessary import class in ExecutionContext.
"import org.springframework.util.Assert;"
Add BeanCreationException to list of standard failure exceptions

Without this change, when passing an invalid job parameter to a bean
that is created internally by Spring Batch will cause a
BeanCreationException that is essentially ignored.  Due to it being
ignored, an infinite loop occurs in processing.
Change ClassifierCompositeItemWriter to honor item order

The ClassifierCompositeItemWriter loops through the items passed to the
write method twice.  The first time to classifier each item.  The second
tiem to perform the actual writes (this prevents the unnecessicary IO if
an error occurs during classification).  A HashMap was previously used
to hold the classified items (key to the writer : item) however this
causes the items to be written out of order.  This update changes it to
a LinkedHashMap to honor the order the items come in.
Added test to DelimitedLineTokenizer based on StackOverflow Question

A question was asked on StackOverflow
(http://stackoverflow.com/questions/25914945/spring-batch-delimitedlinetokenizer-with-line-breaks-newline-in-csv)
in which a row wasn't being parsed as expected.  We didn't have a test
for that specific scenario so this commit adds one.
Conditionally add custom scopes when using XML configuration

When using a combination of Java configuration and the XML namespace
configuration, prior to this commit, we would add the batch custom
scopes twice which lead to issues.  This commit gives priority to the
custom scopes provided by the java configuration.  If you've used
@EnableBatchProcessing and have configured batch components using the
batch namespace, the custom scopes that come with the java config will
take precidence.

This commit addresses Jira BATCH-2266