You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by Christoph Reck <Ch...@dlr.de> on 2000/12/08 13:46:19 UTC

JTest [was Re: [PATCH] MethodMap fixed!]

With a clean Vel snapshot the testsuite runs.

When I compile my classes outside of ant (with JBuilder
using the same JDK) into ../bin/classes I get the JTest error:
  Could not invoke the suite() method

When I delete the ../bin/classes (to rely only on 
the vel.jar) I get a message:
  Suite class "org.apache.velocity.test.TemplateTestCase" not found
even though it is in the jar.

This is a real strange behaviour.

So the only way to go is to make changes in src/java/org/...
and then make a new `build-velocity.sh jar test`. This implies 
that I will be having three different sets of classes: the jar
file, the JBuilder compiled ones and the ant compiled ones :.(

Currently I was keeping my changes in bin/src/org/... to provide
the diffs of my patches, but the build overwrites them with
the originals from src/java/org/... The workaround is to keep
a copy of the original somewhere else until I got our Admins
to open the CVS port (and IRC) - damn bureaucracy.

:) Christoph


> > On my solaris box I cannot run the testbed. Running
> > "build-velocity.sh test" I get:
> >         Buildfile: build-velocity.xml
> >
> >         test:
> >         Running JUnit template tests for Velocity ...
> >         Could not invoke the suite() method
> >
> > I'm using the 20001206 snapshot. I guess it might have something
> > to do with JTest 3.2 and the xerces/xalan 1.2.1 jars?
> > What can be done to get it running again? (restoring xerces breaks ant...)
> > Where can I get a JTest compatible with the new xerces?
> > Is there a way of calling JTest with mannualy setup classpath?
> 
> I'm not so sure that's the reason.  I hope it is, but not convinced.
> When I was doing the #set() recently, I ran into the same thing.  I was
> seeing some bizarre behavior / side-effects from the parser at that
> time, and when I backed out / modified parser changes it worked again.
> I didn't have the time to chase it down, but I guess i should have. :)
> 
> Is that a clean 20001206 snapshot with just your patches?  Or have you
> modified other things?
> 
> geir
> 
> > :) Christoph