Build #19

Gradle build for Spring Batch

Build: #19 failed Changes by Michael Minella

Build result summary

Details

Completed
Duration
2 minutes
Labels
None
Agent
bamboo-19.af.pivotal.io
Revision
32694a5a6c697c07575cfd5e15a7217ae7cf14c6 32694a5a6c697c07575cfd5e15a7217ae7cf14c6
Total tests
1914
Fixed in
#20 (Changes by Yanming Zhou <zhouyanming@gmail.com>)

Tests

Responsible

Code commits

Author Commit Message Commit date
Michael Minella Michael Minella 32694a5a6c697c07575cfd5e15a7217ae7cf14c6 32694a5a6c697c07575cfd5e15a7217ae7cf14c6 Added comparitor for state transitions when using java config
Spring Batch orders the transitions as it goes from state to state based
on specificity.  The XML configuration has always had this
functionality.  However, when creating the JSR-352 implementation, the
mechanism for which this occured was refactored.  That occured at about
the same time as the java builders were introduced.  Because of this
crossing of paths, the java configuration option for defining jobs has
never correctly sorted the transitions.  This PR applys the sorting
algorithm to the java configuration, making XML and java configuration
behave the same.

Resolves #3638

(cherry picked from commit 8e8f9c8101b52b64050d8e92363de2d28319e3b0)

Tests

New test failures 1
Status Test View job Duration
Collapse Failed JsrSplitParsingTests test History
Default Job < 1 sec
java.lang.AssertionError: java.lang.AssertionError: expected:<COMPLETED> but was:<FAILED>
java.lang.AssertionError: expected:<COMPLETED> but was:<FAILED>
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.failNotEquals(Assert.java:834)
	at org.junit.Assert.assertEquals(Assert.java:118)
	at org.junit.Assert.assertEquals(Assert.java:144)
	at org.springframework.batch.core.jsr.configuration.xml.JsrSplitParsingTests.test(JsrSplitParsingTests.java:49)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
(46 more lines...)

Jira issues

IssueDescriptionStatus
Unknown Issue TypeJSR-352Could not obtain issue details from Jira