commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Bodewig <bode...@apache.org>
Subject [Jelly] Lessons from Gump part 2: Ant tags test swallow valuable information
Date Wed, 14 Apr 2004 14:33:25 GMT
Something that really caused me a lot of trouble while I should have
known about it (since I'm familiar enough with Ant).

The jelly-tags-ant build failed up until recently - and fails against
any released version of Ant 1.6.x - because Jelly doesn't set the
ant.file property that Ant expected to be set.  Patch for this in
lesson 3.

The main problem for me was that the stack traces visible in the build
log showed
org.apache.commons.jelly.tags.ant.AntTag.doTag(AntTag.java:186) as the
top most stack frame while the real exception happened somewhere
inside Ant.

Ant's <junit> task has a filtertrace attribute that is true by
default.  If set, Ant will filter out all stack-frames from inside Ant
and JUnit classes when printing the exceptions.  So for all jelly-tag
builds that use Ant indirectly - i.e. jelly-tags-ant and those derived
from it, the filtertrace attribute should be set to false.

I know that Jelly's build files have been generated by Maven but I
don't know whether it is possible to set this attribute via Maven.  It
would be nice if you could somehow change the build files for the Ant
and JSL tag libraries.

Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message