Hi,
When I try and instantiate a DefaultConfigurationBuilder in my JUnit test case, which is called from an Ant script something very odd happens. The instantiation fails but no exception is thrown. Obviously the tests then have errors in them.
This is my classpath:
CLASSPATH=C:\java\jdk1.3.1_08\lib\rt.jar;C:\java\jdk1.3.1_08\lib\tools.jar;c :\java\junit3.8.1\junit.jar;C:\java\jakarta\avalon\Avalon-4.1.4\avalon-frame work-4.1.4.jar;C:\java\xerces-1_4_4\xerces.jar
I've attached my sourcecode and build.xml. Even as I read this mail it sounds to me like I'm failing to spot something retina-burstingly obvious but I'd really appreciate it if someone could help. Or recommend decent medication maybe...
ANT has its own classpath management. What we have done is to set up a set of paths at the beginning of the ANT build script.
In the test target, we supply the <classpath refid="test.class.path"/> which has all that is needed for configuration reading.
If no exception is thrown, it is hard to figure out what is going on. Do you have the "throws Exception" clause on your test method and setUp/ tearDown methods?
-- "You know the world is going crazy when the best rapper is a white guy, the best golfer is a black guy, The Swiss hold the America's Cup, France is accusing the US of arrogance, and Germany doesn't want to go to war. And the 3 most powerful men in America are named 'Bush', 'Dick', and 'Colon' (sic)".
-----Chris Rock
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
