From: "Morgan Delagrange" <[EMAIL PROTECTED]>
> --- James Strachan <[EMAIL PROTECTED]> wrote:
> > From: "Morgan Delagrange" <[EMAIL PROTECTED]>
> > > You were able to reproduce the error?  You're
> > further
> > > along than me.  The email threads above seem to
> > > suggest a problem between Ant and BeanUtils, but
> > when
> > > I try Maven with the the HEAD versions, Maven just
> > > silently exits with BUILD SUCCESSFUL.
> >
> > Try just changing the ant version to some made up
> > token (say 'dev') then
> > copying CVS HEAD builds of Ant into your local maven
> > repo as ant-dev.jar
> > (and ant-optional-dev.jar) and you should get the
> > same error.
>
> I finally zeroed in on it by using the Ant script (ran
> it once, replaced the ant libs with HEAD, and then ran
> it again with JAR downloading off).  It's kind of
> goofy that log.error(Exception) doesn't print out
> stack traces.  :P

Agreed. Its always suprised me that one.


> I noticed that in one place the AntTag class catches
> Throwable.  Is that intentional?  Throwable catches
> all sorts of important errors potentially unrelated to
> Jelly.  Shouldn't that be Exception or a specific set
> of Exceptions?

I forget now but I think the reasoning behind that was so that someone could
catch Throwable exceptions in Jelly scripts.


> Cool.  I just tried it with the Ant build, and it
> passes, although there was a block of error messages:
>
>     [junit] [ERROR] AntTag - -Class
> org.apache.commons.jelly.tags.junit.CaseTag

I get the same, irrespectively of the Ant version I try (HEAD or 1.5.1). Am
a little stumped. Most of my testing up to now has been inside Maven. This
could be a class loader problem when using Ant, as Stefan mentioned.  Though
at least the tests don't actually fail, so it shouldn't break the Gump build
:-)

James
-------
http://radio.weblogs.com/0112098/

__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to