[EMAIL PROTECTED] wrote:
Author: antelder
Date: Tue Aug 5 03:44:07 2008
New Revision: 682663
URL: http://svn.apache.org/viewvc?rev=682663&view=rev
Log:
Update for latest jms binding code
Modified:
tuscany/java/sca/itest/validation/src/test/java/binding/jms/DoesntProcessHeadersTestCase.java
Modified:
tuscany/java/sca/itest/validation/src/test/java/binding/jms/DoesntProcessHeadersTestCase.java
URL:
http://svn.apache.org/viewvc/tuscany/java/sca/itest/validation/src/test/java/binding/jms/DoesntProcessHeadersTestCase.java?rev=682663&r1=682662&r2=682663&view=diff
==============================================================================
---
tuscany/java/sca/itest/validation/src/test/java/binding/jms/DoesntProcessHeadersTestCase.java
(original)
+++
tuscany/java/sca/itest/validation/src/test/java/binding/jms/DoesntProcessHeadersTestCase.java
Tue Aug 5 03:44:07 2008
@@ -55,6 +55,6 @@
Problem problem =
((DefaultLoggingMonitorImpl)monitor).getLastLoggedProblem();
assertNotNull(problem);
- assertEquals("DoesntProcessHeaders", problem.getMessageId());
+// assertEquals("DoesntProcessHeaders", problem.getMessageId());
}
}
It looks like this change has just bypassed the test failure.
Is anyone looking into the real cause of the failure? I don't
see a JIRA open for this, so I have opened a blocking JIRA
TUSCANY-2532 and I have marked this test with an @Ignore annotation
referencing this JIRA (committed as r683210). In future I think
it would be good practice to do this for all build break test case
failures.
Simon
