Hi,
this is a first of several mails in a loose series while I try to
build as much of Jelly as possible within Gump. You may have seen
Gump nag mails appear and disappear over the past weeks and I want to
tell you what we had to do make some of the failures go away.
The first set of failures appeared when we didn't explicitly use
Xerces in the forked <junit> tests of the JUnit taglib. If we use the
version of Crimson that is part of JDK 1.4.2 the unit tests fail with
[junit] Testcase: assertThrowsTests took 0,131 sec
[junit] Caused an ERROR
[junit]
file:/javastuff/gump/jelly-tags/junit/target/test-classes/org/apache/commons/jelly/tags/junit/suite.jelly:118:-1:
<test:assert>
file:/javastuff/gump/jelly-tags/junit/target/test-classes/org/apache/commons/jelly/tags/junit/suite.jelly:118:-1:
<test:assert> columnNumber not set. Assertion failed while evaluating test:
${ex.columnNumber gt 0}
[junit] org.apache.commons.jelly.JellyTagException:
file:/javastuff/gump/jelly-tags/junit/target/test-classes/org/apache/commons/jelly/tags/junit/suite.jelly:118:-1:
<test:assert>
file:/javastuff/gump/jelly-tags/junit/target/test-classes/org/apache/commons/jelly/tags/junit/suite.jelly:118:-1:
<test:assert> columnNumber not set. Assertion failed while evaluating test:
${ex.columnNumber gt 0}
[junit] at
org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:661)
[junit] at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:250)
[junit] at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:89)
[junit] at
org.apache.commons.jelly.tags.junit.CaseTag$1.runTest(CaseTag.java:59)
[junit] Caused by: org.apache.commons.jelly.tags.junit.JellyAssertionFailedError:
file:/javastuff/gump/jelly-tags/junit/target/test-classes/org/apache/commons/jelly/tags/junit/suite.jelly:118:-1:
<test:assert> columnNumber not set. Assertion failed while evaluating test:
${ex.columnNumber gt 0}
[junit] at
org.apache.commons.jelly.tags.junit.AssertTagSupport.fail(AssertTagSupport.java:39)
[junit] at
org.apache.commons.jelly.tags.junit.AssertTagSupport.fail(AssertTagSupport.java:50)
[junit] at
org.apache.commons.jelly.tags.junit.AssertTag.doTag(AssertTag.java:58)
[junit] at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:233)
[junit] ... 11 more
[junit] Root cause
[junit] org.apache.commons.jelly.tags.junit.JellyAssertionFailedError:
file:/javastuff/gump/jelly-tags/junit/target/test-classes/org/apache/commons/jelly/tags/junit/suite.jelly:118:-1:
<test:assert> columnNumber not set. Assertion failed while evaluating test:
${ex.columnNumber gt 0}
[junit] at
org.apache.commons.jelly.tags.junit.AssertTagSupport.fail(AssertTagSupport.java:39)
[junit] at
org.apache.commons.jelly.tags.junit.AssertTagSupport.fail(AssertTagSupport.java:50)
[junit] at
org.apache.commons.jelly.tags.junit.AssertTag.doTag(AssertTag.java:58)
[junit] at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:233)
[junit] at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:89)
[junit] at
org.apache.commons.jelly.tags.junit.CaseTag$1.runTest(CaseTag.java:59)
It seems as if the location provided by Crimson will not contain the
column number.
I'm not sure whether this is a known issue, just wanted to point it
out.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
